-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Potential incompatibility with next@4.2.12 #1076
Comments
We are experiencing the following, is it related?
|
@Xunnamius are there any steps you need from me to get this into a version we can use? The "bug" is currently inhibiting our CI pipelines, so we would be very happy to use this small fix. |
I was going to push both Pages and App router fixes in the same release, but I can cut a patch release with just this fix 👍🏿 |
I have a room full of developers here who would greatly appreciate that ❤️ |
|
### [4.0.11](v4.0.10...v4.0.11) (2024-09-18) #### 🪄 Fixes * **src:** stop Next.js from attempting to statically generate routes under test ([a461e81](a461e81)) <sup>closes [#1076](https://github.com/Xunnamius/next-test-api-route-handler/issues/1076)</sup>
🎉 This issue has been resolved in version 4.0.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The problem
Looks like the internals have shifted with this version of Next. Investigating.
Semi-related: looks like there might be a bug in https://github.com/vercel/next.js/blame/ac4a1c6730672bf2783414e51f64b49519ddffdb/packages/next/src/server/route-modules/app-route/module.ts#L520-L521 (is one of those
POST
s supposed to be aPUT
?)UPDATE: narrowed down the issue to
isStaticGeneration
being set totrue
in theAsyncLocalStorage
instance context triggering the problematic static generation logic. Looks like some API routes are gonna get statically generated now.Fix incoming.
Reproduction steps
See failing actions.
The text was updated successfully, but these errors were encountered: