Build failing after moving from 13.4.19 to 13.5.6 #57277
Comments
This comment has been minimized.
This comment has been minimized.
|
We're experiencing the same issue. Does this occur when the NODE_ENV environment variable is set to "production", or only when it is set to "development" and other custom values? |
|
I am getting this error: > Export encountered errors on following paths:
/auth-callback/page: /auth-callback
/dashboard/page: /dashboardAnd only appears in production while i run the |
|
The static page generation is annoying. There should be an option to generate static content on demand instead of at build time. |
|
I have the same issue, static build fails because I use cookies with a JWT everywhere. |
|
Same, upgraded from 13.4.19 to 13.5.4 and 13.5.6, builds are now failing with the same code. |
|
The error is still present with 14.0.0. I have two custom error pages, one for |
This comment has been minimized.
This comment has been minimized.
|
It worked for me with |
|
Unfortunately we weren't as lucky as yanickrochon: We upgraded from 13.4.19 to 14.0.1 and stumbled upon pretty similar issues as what Dank-del reported in the initial issue. The same issue also appears with versions 13.5.6 and the latest canary: 14.0.2-canary.21. Specifically, we see the errors for the same 404 and 500 paths as Dank-del (in addition to some of our own paths), but I guess there could still be something wrong with our layout.tsx. I checked https://nextjs.org/docs/messages/prerender-error but I can't see anything that would apply to our case, specifically:
Are others still experiencing this issue with next 14.0.1 or later? Is https://github.com/cubik-so/cubik still failing with the newest version? |
|
The error message is the same as what I encountered. The reason my project faced this issue was due to an issue with environment variables. Note that there is this description here: 
After trying the command 'NODE_ENV=production next', the build was successful. |
This comment has been minimized.
This comment has been minimized.
|
I downgraded to next 13.2.4 and the issue is fixed. I'll wait for a proper fix here, hoping future versions will fix this. |
|
The NODE_ENV has nothing to do with it in my case, just tried it again with 
It tries to generate 19 (!) static pages And this is building with version 
|
|
Following up on this issue. Getting an untraceable error with prerendering. Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: o is not a function
at 4187 (/my/little/project/.next/server/chunks/398.js:1:27611)
at t (/my/little/project/.next/server/webpack-runtime.js:1:127)
at 4950 (/my/little/project/.next/server/chunks/398.js:1:37888)
at t (/my/little/project/.next/server/webpack-runtime.js:1:127)
at 265 (/my/little/project/.next/server/chunks/398.js:17:93235)
at t (/my/little/project/.next/server/webpack-runtime.js:1:127)
at 7622 (/my/little/project/.next/server/app/admin/login/page.js:1:3376)
at t (/my/little/project/.next/server/webpack-runtime.js:1:127)
at F (/my/little/project/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:91961) |
For me, the environment variables make a difference. With
This occurs to me, too. Suddenly, it tries to build many more pages than are present in the source code. Is anyone experiencing this issue using the pages directory, or only the app directory? For my case it occurs with the app dir. |
I'm getting the same issue with the app dir |
|
I used .
└── root-folder /
├── pages/
│ ├── _app.tsx
│ ├── 404.tsx
│ ├── [...url].tsx
│ ├── page-a.tsx
│ └── page-b.tsx
├── src/
│ ├── app/
│ │ ├── app-provider.tsx
│ │ └── app-config.tsx
│ ├── pages/
│ │ ├── page-a
│ │ └── page-b
│ ├── widgets/
│ │ └── -
│ └── shared/
│ └── ui/
│ └── -
└── next.config.jsStarting with ○ Compiling /[...url] ...
✓ Compiled /[...url] in 16.3s (3611 modules)
○ Compiling /not-found ...
✓ Compiled /not-found in 8s (4062 modules)When I change ○ Compiling /404 ...
✓ Compiled /404 in 6.8s (1491 modules)I don't know what next.js team introduced, but maybe this can help somehow to resolve error pages existence. |
|
Looks like there was regression introduced here: #57784 |
|
@huozhi ^^ |
|
This is even now more of an issue since nextjs 13.4.19 introduced a vulnerability: Regular Expression Denial of Service (ReDoS) [High Severity][https://security.snyk.io/vuln/SNYK-JS-ZOD-5925617] in zod@3.21.4 |
|
This is solved for me as of 14.0.4-canary.9 It's probably fixed by this PR: #58609 |
Not for me |
|
not fixed even in 14th ver., had to downgrade |
|
Really annoying and issue and it overlooks common scenarios (e.g environment variables only available when container is deployed). |
huozhi
added
linear: next
|
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate. Why was this issue marked with the
|
|
I went through the comments above that seems could caused by different issues, the original reproduction link in the issue is 404 for me. Would be super helpful if anyone can post a reproduction with their specific case which can help us address this issue. Thanks |
|
Hopefully this is relevant: This sandbox demonstrates how upgrading from next@13.4.12 to 13.5.6 prevents the resolving and importing of the 'leaflet.gridlayer.googlemutant' module, which has no dependencies of its own. I have verified that the module exists in node_modules. (The sandbox uses v13.5.6, so you would need to downgrade to 13.4.12 to see that the issue does not exist in that version.) |
|
@charleskoehl you linked to the official (empty) reproduction template. I'll close this issue as there has been no meaningful activity for over a months since this comment: #57277 (comment) If you still experience this issue, please open a new one with an attached reproduction. 🙏 |
|
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
and others
Link to the code that reproduces this issue
https://github.com/cubik-so/cubik
To Reproduce
apps/cubik-webpnpm installpnpm build --filter=cubik-webCurrent vs. Expected behavior
Current behavior:
Expected behavior: successful build
Verify canary release
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:34 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T8103 Binaries: Node: 20.8.1 npm: 10.1.0 Yarn: 1.22.19 pnpm: 8.9.2 Relevant Packages: next: 13.5.6 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: N/A Next.js Config: output: N/AWhich area(s) are affected? (Select all that apply)
App Router
Additional context
NEXT-2298
The text was updated successfully, but these errors were encountered: