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
[BUG] npm install --package-lock-only crashes with install-strategy=linked in workspaces: Cannot read properties of undefined (reading 'children') #9105
Running npm install --package-lock-only in a monorepo with install-strategy = "linked" in .npmrc crashes with:
npm warn reify The "linked" install strategy is EXPERIMENTAL and may contain bugs.
npm error Cannot read properties of undefined (reading 'children')
This also breaks any tool that internally relies on npm install --package-lock-only to sync the root lockfile — in our case, lerna version (Lerna v9.0.6).
Expected Behavior
npm install --package-lock-only should work correctly with install-strategy = "linked", or at minimum produce a meaningful error message instead of crashing with an unhandled TypeError.
lerna info auto-confirmed
lerna info execute Skipping releases
lerna ERR! Error: Command failed with exit code 1: npm install --package-lock-only --ignore-scripts
lerna ERR! npm warn reify The "linked" install strategy is EXPERIMENTAL and may contain bugs.
lerna ERR! npm error Cannot read properties of undefined (reading 'children')
Passing run (with --install-strategy=hoisted override):
lerna info auto-confirmed
lerna info execute Skipping releases
lerna info lifecycle lerna-monorepo@1.0.3~postversion: lerna-monorepo@1.0.3
✔ bumping version in package.json from 1.0.3 to 1.0.4
✔ bumping version in package-lock.json from 1.0.3 to 1.0.4
✔ outputting changes to CHANGELOG.md
lerna info git Pushing tags...
lerna success version finished
Both runs use the same codebase — the only difference is the npmClientArgs workaround in lerna.json
Environment
npm: 11.11.1
Node: v24.x
OS: ubuntu-latest (GitHub Actions), also reproduced on macOS Darwin arm64
Activity
manzoorwanijk commentedon Mar 12, 2026
It seems to be a regression caused by #9031.
I have created a fix #9108