-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Make build faster #4362
Make build faster #4362
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
🟢 CI successful 🟢Thanks |
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.
I am for this for incremental builds. Is it worth force-enabling this during release (CI) builds? I realise that we haven't explicitly turned it on but lto can have pretty significant perf gains (between a few percent to 20 percent, from memory).
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.
LGTM, but since it mostly affects Turborepo someone from Turborepo should better review it
## What * reland #50830 * remove Object.hasOwn * fix CSS chunks in edge runtime ## Turbopack Changes * vercel/turbo#5253 <!-- OJ Kwon - fix(turbopack): enable runtime flag --> * vercel/turbo#5295 <!-- Will Binns-Smith - remove `__internal_nextjs_integration_test` compile-time feature --> * vercel/turbo#4362 <!-- Donny/강동윤 - Make build faster --> * vercel/turbo#5352 <!-- Tobias Koppers - only wait for JS chunks in none runtime backend -->
Description
We may need to revert these patches from CI
Testing Instructions
fix WEB-812 (link)