mirror of
https://github.com/ether/etherpad-lite.git
synced 2026-05-05 12:16:45 +02:00
372ea3be94
Plugin CI is still failing on ERR_PNPM_IGNORED_BUILDS even with the build-script policy declared in both pnpm-workspace.yaml (#7523) and package.json (#7525). pnpm's strict-dep-builds defaults to true in 10+, so any transitive dep with an unrecognized postinstall fails the build. For etherpad-lite — and especially for downstream plugin repos that pull this codebase as their core install — that's a footgun: the moment some new transitive ships a postinstall, every plugin's CI explodes. Set strictDepBuilds: false in pnpm-workspace.yaml AND strict-dep-builds=false in .npmrc as a defensive layer, so unknown postinstalls become a warning instead of a hard failure. The allow/ignore lists still control what actually runs. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
18 lines
590 B
YAML
18 lines
590 B
YAML
packages:
|
|
- src
|
|
- admin
|
|
- bin
|
|
- doc
|
|
- ui
|
|
onlyBuiltDependencies:
|
|
- esbuild
|
|
# Explicitly ignore build scripts we don't want to run. Listing them here
|
|
# stops pnpm from failing with ERR_PNPM_IGNORED_BUILDS when they're
|
|
# encountered as transitive deps (e.g. scarf pulled in via swagger-ui-dist).
|
|
ignoredBuiltDependencies:
|
|
- '@scarf/scarf'
|
|
# Belt-and-suspenders: even if a fresh transitive dep slips through with a
|
|
# postinstall script, downgrade to a warning so CI doesn't break for
|
|
# downstream plugin repos that pull etherpad-lite as their core install.
|
|
strictDepBuilds: false
|