next-loader | Next Generation EFI-Based Boot Manager

I've found what was my problem. In the i18next documentation says that I should run the init inside the webpack.config.js.

My initial problem was loading the locales. The i18n couldn't find the files after the build, because the webpack doesn't recognize the i18n-xhr-backend requiring the .json files. Then, after the build, there was no translation files. Then, I've tried to let webpack deal with the i18n, and I got another problem, on next paragraph.

The React needs the i18n instance to be add to the i18nextProvider. But, on the way that I was doing, there was no i18n instance to refence inside React. Then, it coudn't find the translation function and whatever else. I've also found the i18nWebpackPlugin, but it also haven't solved my problem, because it also don't give access to the i18n instance inside react. At the end, I had two unsolved problems.

My solution was quite simple. I've created a new i18n config to the development env, and let the webpack deal with the .json, copying it to a new folder after build. I'll let below my config files for webpack and i18n. My steps where:

• Bring i18n.init() back to i18n/index.js
• Create different options for each environment
• Configure webpack to copy translation files
• Import the i18n instance on App.js again

Now, everything works like charm.

OBS: To webpack recognize the .json files, you need to import it somewhere. I did inside the resources.js file.

webpack.prod.config.js