You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pnpm install fails in CI/downstream builds: [ERR_PNPM_IGNORED_BUILDS] for esbuild #1195
pnpm install exits non-zero from a fresh checkout or release tarball.
This breaks downstream packaging (AUR, Nix, Docker) and any CI using set -e.
[ERR_PNPM_IGNORED_BUILDS] Ignored build scripts: esbuild@0.25.8
Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.
To reproduce
curl -sL https://github.com/Fission-AI/OpenSpec/archive/v1.4.1.tar.gz | tar xz
cd OpenSpec-1.4.1
pnpm install
Expected behavior
pnpm install exits 0.
Root cause
The repository has no pnpm-workspace.yaml. In pnpm 10+, build scripts for
all dependencies are blocked by default unless explicitly approved via allowBuilds in the workspace config.
esbuild@0.25.8 (transitive dependency of vitest → vite) has a
postinstall script that downloads a platform-specific binary. Since no
config authorizes it, pnpm blocks it and exits with ERR_PNPM_IGNORED_BUILDS. The TypeScript compilation itself does not need
esbuild, but pnpm treats the unapproved script as a fatal condition.
The file is not gitignored (.gitignore only ignores .pnpm-store/), so
it can be safely committed.
Suggested fix
Commit this pnpm-workspace.yaml to the repository root:
Linked downstream packaging issue: M0Rf30/PKGBUILD#446 / PR #447 — the AUR PKGBUILD currently needs a workaround for this. A fix here will unblock package maintainers.
Fixed by your PR #1196 — thanks for the precise root-cause. The repo now commits pnpm-workspace.yaml with allowBuilds for esbuild plus pnpm.onlyBuiltDependencies in package.json, so pnpm install from a fresh checkout runs the esbuild build script and exits 0. Closing as shipped.
Activity
ismet commentedon Jun 10, 2026
Linked downstream packaging issue: M0Rf30/PKGBUILD#446 / PR #447 — the AUR PKGBUILD currently needs a workaround for this. A fix here will unblock package maintainers.
ismet commentedon Jun 10, 2026
PR submitted: #1196
fix(openspec): allow esbuild build scripts for pnpm 10+ compatibility (…
fix(build): allow esbuild install scripts (Fission-AI#1196)
clay-good commentedon Aug 5, 2026
Fixed by your PR #1196 — thanks for the precise root-cause. The repo now commits
pnpm-workspace.yamlwithallowBuildsfor esbuild pluspnpm.onlyBuiltDependenciesinpackage.json, sopnpm installfrom a fresh checkout runs the esbuild build script and exits 0. Closing as shipped.