Can we change the way namespaces are specified when Next migrate to layouts?

[jasonwilliams]

We don't wish to load all of our namespaces in one go for performance reasons so we use the pages attribute in i18n.js. However our app has many pages so it starts to become too long and unmaintainable.

pages: {
  '*': ['common'],
  '/': ['home'],
...30 lines of more rgx:/toplevel/?.*`
}

Is there a better option to manage this without losing the performance benefits?
Next's big update is a breaking opportunity to try out another format. Like using the folders to put a file into instead? This would help with dynamic routes, be easy to keep track of and tidy up should that route no longer be needed.

Maybe something like..
i18n-namespace.json which lists the namespaces this route uses, this can then be picked up by the scanner. This would also do away with needing regex to handle dynamic routes

Related

• Why do I have to set pages in i18n.js if I still have to reference them in useTranslation()? #857
• https://www.npmjs.com/package/next-translate-scanner

Prior Art

• @shopify/react-i18n will scan the project for translation data and compile from that at build time