Skip to content
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

Problem with next v15 #1229

Open
evgenyatlas opened this issue Nov 7, 2024 · 3 comments
Open

Problem with next v15 #1229

evgenyatlas opened this issue Nov 7, 2024 · 3 comments

Comments

@evgenyatlas
Copy link

What version of this package are you using?
2.6.2

What operating system, Node.js, and npm version?
Mac os, v20.16.0 (npm v10.8.1)

What happened?
Error: Route "/" used searchParams.lang. searchParams` should be awaited before using its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis
at Next_Translate_new__193081f2dd3 (webpack:///app/page.tsx?7603:15:65)
13 |
14 | export default async function Next_Translate_new__193081f2dd3(props) {

15 | const detectedLang = props.params?.lang ?? props.searchParams?.lang
| ^
16 |
17 | if (detectedLang === 'favicon.ico') return <Home {...props} />
18 |`

@dimitribarbot
Copy link

dimitribarbot commented Dec 11, 2024

You can try to use version 3.0.0-canary.5 of next-translate-plugin dev dependency along version 2.6.2 of next-translate.

I've pushed a PR in the next-translate-plugin repository which solves this issue for me while version 3.0.0-canary.5 of next-translate-plugin seems to be fully compatible with the 2.6.2 version of next-translate.

@aralroca
Copy link
Owner

We plan to release 3.0.0 at the end of this year, I need some time to finish some pending things. Please any feedback that Next.js 15 is working fine now would be very appreciated @evgenyatlas . And @dimitribarbot thanks for your contribution 🔥

@zakidze
Copy link

zakidze commented Dec 19, 2024

We plan to release 3.0.0 at the end of this year, I need some time to finish some pending things. Please any feedback that Next.js 15 is working fine now would be very appreciated @evgenyatlas . And @dimitribarbot thanks for your contribution 🔥

cant wait to try it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants