-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
meta: enable turbopack on static mode #8000
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
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enables Turbopack for static export builds and upgrades the Next.js framework from version 15.3.4 to 15.4.2. The change aims to improve build performance by leveraging Turbopack's faster bundling capabilities during static site generation.
- Adds
--turbo
flag to the static export build command - Upgrades Next.js from 15.3.4 to 15.4.2
- Updates eslint-config-next to match the Next.js version
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #8000 +/- ##
==========================================
+ Coverage 73.04% 73.06% +0.01%
==========================================
Files 95 95
Lines 8341 8341
Branches 217 217
==========================================
+ Hits 6093 6094 +1
+ Misses 2247 2246 -1
Partials 1 1 ☔ View full report in Codecov by Sentry. |
Lighthouse Results
|
cc @nodejs/web-infra @nodejs/nodejs-website any idea why turbopack failing on Windows? |
84fdc58
to
87e194f
Compare
87e194f
to
b0c9f6d
Compare
@styfle this looks like a bug in Next.js? It’s seems like it’s trying to combine POSIX and Windows paths? |
@avivkeller would you mind opening a bug on Next.js's repo? I unfortunately have very little time these days 😭 |
Looks like this was fixed on canary here vercel/next.js#81758 and being backported here vercel/next.js#81925 Should land on stable today or tomorrow. |
Thank you, Steven! |
Thanks ! |
Steven is our unsung Next.js hero |
This PR enables Turbopack on Static Export + upgrades to Next.js 15.4.2