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._ does not format values in production build
See original GitHub issueDescribe the bug
When using i18n._ with the second argument “values” those values are not inserted into the string in production build, but they are inserted into the string in development when running npm run start.
To Reproduce I have created a sample repository that can be used to reproduce the problem:
https://github.com/nmoinvaz/lingui-values-bug
Relevant code file: https://github.com/nmoinvaz/lingui-values-bug/blob/main/src/App.js
npm installnpm run start
In development the strings are properly replaced:
npm buildserve -s build
In production the strings are not properly replaced:
Expected behavior
The values object should be inserted into the string. For example {a} should be replaced with 1.
Additional context
- ling-ui version 3.9.0
- Create React App
Issue Analytics
- State:
- Created 2 years ago
- Comments:26 (10 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
Figured it out, works like a charm in development and production builds! Thank you.
Polish some details and I’ll release a new version with this new tool