Replies: 1 comment 2 replies
-
@abarani since version 0.19 all the routing part was moved to Next.js core. So right now next-translate by itself has no way to handle routing. Before version 0.19, there was a "build step" to generate the "pages" directory with all the languages. The change to 0.19 has greatly simplified the library making everything easier, simpler and more comfortable to use. What is the reason to don't want to use the i18n routing of Next.js? I would like to know. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, is it possible to use next-translate without integrating with Next.js i18n routing and rely only on
Accept-Language
header and cookie only?From what I understand adding a locale to the
locales
option ini18n.js
config automatically adds it to the Next.js config and thus enables sub-path routing for the app. What I'm trying to achieve is keeping only a single path for each page but display it localized based solely onAccept-Language
header or cookie (if set). This is for an SSR only app.Great project by the way!
Beta Was this translation helpful? Give feedback.
All reactions