3 ms·
It makes route localization a second-class citizen in the framework at best, or a totally unsupported hack-your-own-solution thing at worst.
by kilburn 4y ago
It makes route localization a second-class citizen in the framework at best, or a totally unsupported hack-your-own-solution thing at worst.
- julianbuse 4y agoif it helps, you could use middleware in next.js to handle routing to separate folders easier.
- kilburn 4y agoMiddleware won't work if you use "next export" to get a truly static site though, which is by far my preferred mode of operation whenever possible. This is what I meant when I said "second-class citizen at best".
- julianbuse 4y agoah I see. Maybe try the route rewriting in next.conf.js? I think thats what the file is. That might work for static sites.
- aj0strow 4y agoIt seems like a path prefix like "/en/books" or "/es/books" could be supported with a base url config. Localized path segments like "/books" or "/libros" could be supported with a path segment mapping configuration. It should work fine in theory. I guess those configs don't exist yet. Or is there something else that route localization requires?