Bump Node heap limit for lint-no-typescript to avoid OOM in CI#90996
Merged
Bump Node heap limit for lint-no-typescript to avoid OOM in CI#90996
Conversation
ijjk
approved these changes
Mar 6, 2026
Collaborator
Tests Passed |
Collaborator
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **402 kB** → **402 kB** ✅ -31 B80 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
sokra
pushed a commit
that referenced
this pull request
Mar 6, 2026
The `lint` job in CI has been hitting `FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory` during `lint-eslint`. `lint-no-typescript` runs `prettier-check`, `lint-eslint .`, and `lint-language` in parallel via `run-p`. The `lint-eslint` script uses `eslint.cli.config.mjs` which enables type-checked rules with `parserOptions.project: true` — the config comment itself notes this "needs a lot of memory". Node's default heap limit caps around ~2-4GB regardless of available system memory, which isn't enough when the type-aware parser loads the full monorepo project graph. This sets `NODE_OPTIONS="--max-old-space-size=8192"` on the `lint-no-typescript` script via `cross-env`. The env var inherits into all three `run-p` children, giving eslint the headroom it needs without touching CI workflow files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
lintjob in CI has been hittingFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryduringlint-eslint.lint-no-typescriptrunsprettier-check,lint-eslint ., andlint-languagein parallel viarun-p. Thelint-eslintscript useseslint.cli.config.mjswhich enables type-checked rules withparserOptions.project: true— the config comment itself notes this "needs a lot of memory". Node's default heap limit caps around ~2-4GB regardless of available system memory, which isn't enough when the type-aware parser loads the full monorepo project graph.This sets
NODE_OPTIONS="--max-old-space-size=8192"on thelint-no-typescriptscript viacross-env. The env var inherits into all threerun-pchildren, giving eslint the headroom it needs without touching CI workflow files.