-
-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't set localeDetection in the next-i18next.config #2049
Comments
Seems to work in this example: https://github.com/i18next/next-i18next/tree/master/examples/simple |
so I found its because of the lines above next-i18next.config.js which prevent that this error appear: Line 18 in cc1d9d1
|
And why do you want to remove this?
Maybe @belgattitude can help? |
Thx for mention, I'm still off a couple of days but I'll read properly soon and see what we can do. |
Probably we removed it earlier by accident. But to me, it looks like with this, the error didn't show up although the interface from your and next config differ at this point. but I'm not quite sure about it. |
It will be fixed in #2057. In the meantime, you can safely remove the typecheck in the config
|
Released in 13.0.1 |
changing that to |
We're also getting
for the export default appWithTranslation<AppProps>(
App,
nextI18NextConfig,
); Is there any cleaner way of fixing this than to cast the export default appWithTranslation<AppProps>(
App,
nextI18NextConfig as UserConfig,
); |
We are having the same issue. `import { serverSideTranslations } from "next-i18next/serverSideTranslations"; export async function getServerSideProps(context) {
|
I hope everything is alright since this is my very first report.
I just tried to upgrade my nextjs application. Which worked fine so far. But when I try to build the application I get an error:
🐛 Bug Report
To Reproduce
the next-i18next.config.js looks like this:
our _app.page.tsx looks like this:
Expected behaviour
I would expect that the method appWithTranslation/UserConfig accepts the property localeDetection. Since nextjs would accept it by default.
I used this approach to always have the language in the URL https://nextjs.org/docs/advanced-features/i18n-routing
Our Environment
node v16.14.0
"next": "13.0.6",
"next-i18next": "^13.0.0",
"i18next": "^22.0.8",
"react-i18next": "^12.0.0",
The text was updated successfully, but these errors were encountered: