package-lock.json does not match package.json
Error recorded 2 times in PanelAlpha Engine deploys on Express. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen2 times
WhereExpress
StatusResolve ReadyOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
npm ci installs only from a package-lock.json that matches package.json, and this one is missing entries (for example @types/react). The deploy log shows npm's usage text instead of that reason.
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…