Closed mikeesto closed 3 weeks ago
Thanks for opening this!
@ovflowd I believe this will be fixed in https://github.com/vercel/turbo/pull/8303
@wbinnssmith Do you know when this fix will be available in Next.js?
This has been fixed in canary, thanks!
https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.13
This has been fixed in canary, thanks!
https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.13
Will it be backported to 14x?
Because I'm not sure what other sort of breaking changes we need to 👀 for Next.js v15
I spoke to @ztanner and we are expecting to release a patch to v14 sometime in the next week or two.
still happing in 14.2.4 (turbo), for me.
still happing in 14.2.4 (turbo), for me.
You should report this as a bug on Vercel's turbo repository, not here :)
We had to disable the
--turbo
flag in the development script due to an error when updating to Nextjs 14.2 (https://github.com/nodejs/nodejs.org/pull/6803). It would be good to re-enable it once the underlying issue is resolved.Steps to Reproduce
--turbo
flag in the dev script.Expected Behavior The development server should run without errors with the
--turbo
flag enabled.