-
Notifications
You must be signed in to change notification settings - Fork 28.3k
i18n handling #103
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
The yaml error you're seeing is because next's webpack configuration doesn't include yaml files out of the box. In next.js v2.0.0 you can add them using https://github.com/zeit/next.js#customizing-webpack-config. For your second question. v2.0.0 has a |
I don't understand why loader syntax is not supported in nextjs out of the box though. Is that decision made in the past? |
@pencilcheck Check out this ticket 👍 #1245 |
Looks like there is a positive outcome, but not until 3.0... a long wait. Thanks for referring to the ticket. :) |
Hello, this is a question/discussion about the proper/suggested way to handle i18n.
What I have (on my current app that I'm thinking to port to next) right now is: multiple LOCALE.yaml files (as I use localeapp to easily manage multiple locales) i.e.
therefore inside my react components I can use
The things are:
/pages/index.js
but it's not working, and the error is thrown once I load the page ({ [Error: Cannot find module 'json!yaml!../config/locales/en.yml'] code: 'MODULE_NOT_FOUND' }
).ty!
The text was updated successfully, but these errors were encountered: