Open simonknittel opened 4 months ago
Hi @simonknittel , For clarity, has this worked for you prior to this SDK version? (Turbopack)
Hi @andreas-unleash, I tested with following combinations of version:
1.4.2 | 1.4.1 | 1.4.0 | |
---|---|---|---|
14.2.3 | ❌ | ❌ | ❌ |
14.2.0 | ❌ | ||
14.1.3 | ✅ | ✅ |
It seems to me, that it broke with Next.js v14.2+, independent of the SDK version.
Thanks @simonknittel . My guess is that NextJS changed something in Turbopack. We will definitely look into it but you did say that not using Turbopack does not give you the error right?
Yes, it's only an issue when using Turbopack.
I'm aware that Turbopack isn't fully production ready yet, but I thought to give you an heads-up 🙂
Describe the bug
Seems like the issue from #32 is back but this time only when using
npx dev --turbo
. Without--turbo
it's working fine.Steps to reproduce the bug
@unleash/next.js@1.4.2
Example:
Expected behavior
The server-side methods should not use any client-side methods.
Logs, error output, etc.
Screenshots
Additional context
Next.js v14.2.3
Unleash version
5.11.3
Subscription type
Open source
Hosting type
Self-hosted
SDK information (language and version)
@unleash/next.js@1.4.2