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
Recently, we've been getting Node 22 CI failures, notably on the Dependabot PRs which can no longer be merged immediately even if valid:
The "Install Dependencies" step gives this output:
Run npm ci --no-fund
npm error code EUSAGE
npm error
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm error
npm error Missing: typescript@5.9.3 from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci"for more info
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-09-01T05_13_11_523Z-debug-0.log
Error: Process completed with exit code 1.
Describe the solution you'd like
Investigate the cause of the bug and implement a fix. It might be as simple as pinning an NPM version for the runners so they don't disagree when resolving package-lock.json contents.
Additional context
Related, TS bump PR which might have triggered this: #1602
Activity