package-lock.json is out of date with package.json

The project's package-lock.json does not match its package.json (npm: Missing: @types/[email protected] from lock file), and npm ci installs only from a lockfile that does. Regenerate it with npm install and commit it.

Seen2 times
WhereExpress

Why it happens

npm ci installs only from a lockfile that matches package.json, and this lockfile is missing a package that package.json now requires (the React type definitions). The engine showed npm's usage text instead of this reason; that is being fixed.

What the log looks like

Deploy log
npm error [--allow-scripts <package-list> [--allow-scripts <package-list> ...]]npm error [--strict-allow-scripts] [--dangerously-allow-all-scripts] [--no-audit]npm error [--no-bin-links] [--no-fund] [--dry-run]npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]npm error [--workspaces] [--include-workspace-root] [--install-links]npm errornpm error   --install-strategynpm error     Sets the strategy for installing packages in node_modules.npm errornpm error   --legacy-bundlingnpm error     Instead of hoisting package installs in `node_modules`, install pac…

Try PanelAlpha Engine yourself.

The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.

Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPURead the documentation