Routing i18n, including translations of slugs.
Unanswered
Brown bear posted this in #help-forum
Brown bearOP
Lots of people seem unthrilled by Next's i18n solutions when it comes to routing (https://github.com/vercel/next.js/discussions/18485)
Using middleware which gets called on every request seems like a barely ok solution.
So far, the best I've found is this package https://github.com/svobik7/next-roots
Opinions, experiences to share about next-roots?
The npm package only gets a few hundreds weekly downloads, are there alternatives I might have overlooked?
Using middleware which gets called on every request seems like a barely ok solution.
So far, the best I've found is this package https://github.com/svobik7/next-roots
Opinions, experiences to share about next-roots?
The npm package only gets a few hundreds weekly downloads, are there alternatives I might have overlooked?
1 Reply
American Crow
I am using next-intl for translation including localized pathnames. But yea it's a Middleware. At the same time they support static generation (unstable) with app router, so that combo is fine with me.