-
Notifications
You must be signed in to change notification settings - Fork 409
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
[TOOL-3032] Next.js build memory optimizations #5938
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5938 +/- ##
=======================================
Coverage 54.85% 54.85%
=======================================
Files 1142 1142
Lines 60928 60928
Branches 5140 5140
=======================================
Hits 33424 33424
Misses 26777 26777
Partials 727 727
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|
Merge activity
|
* Disable eslint as part of next.js build - We are already running eslint in separate pipeline * Enable Next.js memory optimization flags <!-- start pr-codex --> --- ## PR-Codex overview This PR primarily focuses on enhancing the configuration of multiple `Next.js` applications by adding ESLint settings, production source maps, and experimental features. It also modifies security headers and refines the handling of IPFS gateways. ### Detailed summary - Added `eslint` configuration with `ignoreDuringBuilds: true` to multiple `next.config` files. - Set `productionBrowserSourceMaps` to `false`. - Enabled experimental features: `webpackBuildWorker`, `webpackMemoryOptimizations`, and `serverSourceMaps`. - Updated security headers in `apps/dashboard/next.config.ts` for consistent formatting. - Refined `determineIpfsGateways` function for IPFS gateway handling. - Maintained existing configurations for redirects, rewrites, images, and compiler settings. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
PR-Codex overview
This PR introduces several enhancements and configurations for the
next.config
files across multiple applications, focusing on ESLint settings, source maps, and security headers. It also refines the handling of remote IPFS gateways and Sentry options.Detailed summary
eslint
configuration to ignore during builds in multiplenext.config
files.productionBrowserSourceMaps
tofalse
.webpackBuildWorker
,webpackMemoryOptimizations
, andserverSourceMaps
.determineIpfsGateways
function for better client ID handling.SENTRY_OPTIONS
for better source map management and logging.baseNextConfig
structure to include new configurations and maintain existing functionalities.