Lionel Rudaz
Lionel Rudaz
Same here. It caused issues especially with FastBoot, looks like FastBoot was confused when hitting / and there was no session available anymore. I don't know. Have you found a...
What's the workaround?
Same issue with AI 3.1.9 and Next 14.2.2. My product is not yet on production, so that's OK, but that's bummer if you rely on this feature 😅 I hope...
> It's a Next.js v13.2.4 project running on Node v18. Same here. I'm also deploying on Vercel. Sorry for the delay in my answer. @rektdeckard, does that mean we must...
Got you, I agree this becomes a nightmare for you. Should I open an issue at Vercel's end for that or do you plan to document the workaround? With the...
I've upgraded the library to 2.0.10, was using 2.0.9 before. I wonder if our friends at Vercel haven't changed something at their end, as I haven't added the modularizeImports workaround...
Thanks @unstubbable, that's awesome. Can you point to the Next.js release that we'll have to upgrade to? Will it be 14.3.0 or a minor release of 14.2?
I'm still a bit confused with this one. Should we wait for Next.js 15 to be released or is there a suitable workaround for this? It's still in the docs,...
OK so it seems to work on AI SDK 3.1.x. But when you upgrade to 3.2.x, it breaks again. Any ideas how we can fix that? That's quite annoying as...
Hey @amcclure-super, no I'm using Next 14.2.4. I had to specify this version as it was working with it. What's your Next version?