Issue with Gatsbyjs when building (server side) about react-translate HOT 4 CLOSED

Hi,

Yes, it's supposed to work on the server too. Do you have a minimal repro?

from react-translate.

😄 Yes npm i -g gatsby then gatsby new test-site then cd test-site

create gatsby-browser.js

import React from 'react';
import { TranslatorProvider } from "react-translate";
const translations = require('./i18n');

exports.wrapRootComponent = (Root) => {
  const Wrapper = () => (
    <TranslatorProvider translations={translations}>
      <Root />
    </TranslatorProvider>
  )
  return Wrapper;
}

create pages/home.js

import React from 'react';
const Home = ({ t }) => {
  return (
    <div>
      {t("tagline1")}
    </div>
  );
}
export default translate("Home")(Home);

then if you run gatsby develop and open your browser on localhost:8000/home everything should work fine
as soon as you run gatsby build the problem is that the context is lost and the translate('component')(component) doesn't work anymore, probably because there is no more ancestor <TranslatorProvider>

from react-translate.

gatsbyjs/gatsby#688 (comment)

Do you think it could it be related to this step?
https://github.com/gatsbyjs/gatsby/blob/b4d585a2c0035dc3c8896c42e2daaac1b520be5a/lib/utils/webpack.config.js#L137

case 'build-html':
  config.plugin('static-site-generator', StaticSiteGeneratorPlugin, ['render-page.js', routes])

Seems like you are adding manually routes torender-page.js otherwise it doesn't inherit them automatically from the context of react-router?

I was thinking if I have to do the same and pass the translator function created by the provider but at the moment I have no clear idea how all of this is working.

Could be related to the scope of static-site-generator-webpack?
https://github.com/markdalgleish/static-site-generator-webpack-plugin#scope

At this point I don't think it's related to your package because I get same error when using react-intl.

But if you wanna be nice and helpful I appreciate any hint to fix this.

from react-translate.

Almost solved
gatsbyjs/gatsby#688 (comment)

Not related to your library, I close the issue.

Thank you 😄

from react-translate.