Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
i18n support?
See original GitHub issueAny plans to add support for i18n?
I’ve had previous success with i18n webpack plugin - perhaps this could be integrated into the webpack configuration?
Given that it increases build time significantly (as it makes use of webpack’s multi-compiler feature i.e. module.exports = [configA, configB]; instead of module.exports = config;), it would most likely have to be an opt in feature. We could look for an i18n/ directory that users could drop a bunch of json files into the like so:
src/
i18n/
├─ en-gb.json
├─ de-de.json
├─ ...
The idea that CRA would produce an output bundle per locale in conjunction with i18n webpack plugin.
Thoughts? Happy to attempt a PR if you have no objections.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:54
- Comments:22 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Same here, looking for a the cleanest way to add i18n support into Create React App app without ejecting, maybe there should be some kind of localization section in README?
I agree this is something we’ll need to address.