-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@shopify/react-i18n has broken since v11 (babel bug) #29500
Comments
Please verify that your issue can be recreated with Why was this issue marked with the
|
This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What version of Next.js are you using?
10.2.4-canary.2 and above
What version of Node.js are you using?
15.0.0
What browser are you using?
Chrome
What operating system are you using?
MacOS
How are you deploying your application?
Other
Describe the Bug
We use react-i18n along with Next. It works by using Babel to compile all the translations during the build step. I tried using v11 of Next and translations did not work, i was getting errors or missing translations.
I managed to bisect the versions of Next down to 10.2.4-canary.2 being the issue. Looking at the releases notes I'm assuming the new babel mode has broken it somehow.
The error is:
Expected Behavior
Translations work on our NextJS site
To Reproduce
Working
npm i -f
npm run dev
Failing
10.2.4-canary.2
npm i -f
npm run dev
CC @samrmur
Possibly related to: #26539
The text was updated successfully, but these errors were encountered: