Replies: 3 comments 16 replies
-
|
What's the What about Also, is this just running build again? As in |
Beta Was this translation helpful? Give feedback.
-
|
We are experiencing the same issue with similar setup after upgrading to next 16. App router with This is with using turpoback. The speed of build & deploy CI has decreased by about 30 % going from 7 mins to 10 mins after switching to nextjs 16 because of the increased build size.
|
Beta Was this translation helpful? Give feedback.
-
|
I understand your concern about the increased .next folder size after upgrading to Next.js 16. Here is an explanation and some recommendations to help clarify this behavior. This behavior is expected in Next.js 16 due to changes in the build system and server-side optimizations. Explanation
Recommendations
rm -rf .next
npm run build
Summary The increased |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
We have an app serving about 6k static pages, when using Next.js 15.x, our folder was about 3.5GB, now with Next.js 16 the folder is about 6.3GB.
We want to know if this is normal behavior of the new version, something we have to accept, or if something is wrong with our implementation.
Additional information
This is the distribution of size across my .next folder.
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions