DUNGEONS-34: fix npm 10 startup lockfile failure #3
Reference in New Issue
Block a user
Delete Branch "codex/dungeons-34-npm-lock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
npm run dev:allfailed on Node 22's npm 10.9.8 because the frontend lockfile generated with npm 11 omitted peer dependencies required by npm 10. Regenerate the lockfile from an isolated directory using npm 10, adding the missing parser/plugin/binding records while retaining every previously locked package version.Add
npm run test:installto validate the committed manifests without an existing node_modules directory, and document running it with npm 10 and 11 when updating dependencies. The startup command is unchanged.Validation: reproduced the exact EUSAGE failure; the new regression check fails before the fix and passes with npm 10.9.8 and npm 11.19.1 afterward. The actual launcher with Node 22.23.2/npm 10.9.8 passes dependency installation, production build, page/authentication checks, cached restart, shutdown, and occupied-port checks. Frontend typecheck passes.
Closes DUNGEONS-34