i18n support?
Any plans to add support for i18n? I've had previous success with [i18n webpack plugin](https://webpack.js.org/plugins/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](https://webpack.js.org/plugins/i18n-webpack-plugin/). Thoughts? Happy to attempt a PR if you have no objections.
Posted by matthewdavidson on Nov 23, 2016, 9:05 AM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
i18n support?
Any plans to add support for i18n? I've had previous success with [i18n webpack plugin](https://webpack.js.org/plugins/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](https://webpack.js.org/plugins/i18n-webpack-plugin/). Thoughts? Happy to attempt a PR if you have no objections.
Comments (0)
No comments yet. Start the discussion.