You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Having all translations per language in a single file gets crowded for large projects. It would be nice to split them into multiple files based on namespace
Describe the solution you'd like
Having my translation namespaces as files nested in the messages/en folder and the messages/no folder like so
On a related note, there's now a VSCode integration for next-intl which helps to streamline the management of translations in large files: VSCode integration docs.
Is your feature request related to a problem? Please describe.
Having all translations per language in a single file gets crowded for large projects. It would be nice to split them into multiple files based on namespace
Describe the solution you'd like
Having my translation namespaces as files nested in the messages/en folder and the messages/no folder like so
Describe alternatives you've considered
Manually importing every file with some clever loop in my
layout.tsx
and putting it into my messages.jsonThe text was updated successfully, but these errors were encountered: