Skip to content

build(mac): bump webpack heap to 6 GB on the macOS appbundle build #9967

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.

Sign up for GitHub

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

Merged
asheshv merged 1 commit into from
May 22, 2026
+7 −3
Merged

build(mac): bump webpack heap to 6 GB on the macOS appbundle build #9967

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions pkg/mac/build-functions.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,10 +305,14 @@ _complete_bundle() {
# stderr into stdout, so a crash inside lint/webpack (e.g. an OOM
# kill or native-module load failure) leaves a trace in the
# Jenkins console instead of an empty gap before the trap fires.
# Env vars match the top-level "bundle" npm script (see web/package.json)
# so behavior is identical to `yarn run bundle`.
# NODE_ENV mirrors the top-level "bundle" npm script (see
# web/package.json). NODE_OPTIONS bumps V8's old-space ceiling
# past the 3 GB default the npm script uses: the macOS x64 builder
# OS-OOM-kills webpack inside TerserPlugin at the 3 GB setting
# (build #1294, sealing asset processing at 92%). Other build
# paths still get 3 GB via the npm script.
export NODE_ENV=production
export NODE_OPTIONS=--max-old-space-size=3072
export NODE_OPTIONS=--max-old-space-size=6144
echo "==> Running ESLint..."
yarn run linter 2>&1
echo "==> Running webpack bundle..."
Expand Down
Loading