backend/package-lock.json was out of sync with package.json. Three declared dependencies had no lockfile entry:
node-cron (imported by src/server.ts:1)
node-pg-migrate (imported by tests/integration/setup/testDb.ts:2)
@types/node-cron
Consequences: npm ci fails outright, and a plain npm install silently rewrites the lockfile. On a clean checkout the backend fails to type-check (Cannot find module 'node-cron') and integration tests can't run their migrations.
Regenerated via npm install — no dependency versions changed in package.json, this only adds the missing entries and their transitive deps.
Verification
npx tsc --noEmit — clean (was failing on the missing module before this)
Unit tests — 16/16
Integration tests — 14/14
One note for anyone running these locally: the lockfile now resolves lru-cache v11 transitively, which needs Node ≥ 20.6 (diagnostics_channel.tracingChannel). CI is on Node 20 and fine; local Node 18 will fail in Jest's global setup.
`backend/package-lock.json` was out of sync with `package.json`. Three declared dependencies had no lockfile entry:
- `node-cron` (imported by `src/server.ts:1`)
- `node-pg-migrate` (imported by `tests/integration/setup/testDb.ts:2`)
- `@types/node-cron`
Consequences: `npm ci` fails outright, and a plain `npm install` silently rewrites the lockfile. On a clean checkout the backend fails to type-check (`Cannot find module 'node-cron'`) and integration tests can't run their migrations.
Regenerated via `npm install` — no dependency versions changed in `package.json`, this only adds the missing entries and their transitive deps.
## Verification
- `npx tsc --noEmit` — clean (was failing on the missing module before this)
- Unit tests — 16/16
- Integration tests — 14/14
One note for anyone running these locally: the lockfile now resolves `lru-cache` v11 transitively, which needs Node ≥ 20.6 (`diagnostics_channel.tracingChannel`). CI is on Node 20 and fine; local Node 18 will fail in Jest's global setup.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
node-cron, node-pg-migrate, and @types/node-cron are declared in
package.json but were missing from the lockfile, so npm ci fails and a
plain npm install silently rewrites the lock. Regenerated to match.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
backend/package-lock.jsonwas out of sync withpackage.json. Three declared dependencies had no lockfile entry:node-cron(imported bysrc/server.ts:1)node-pg-migrate(imported bytests/integration/setup/testDb.ts:2)@types/node-cronConsequences:
npm cifails outright, and a plainnpm installsilently rewrites the lockfile. On a clean checkout the backend fails to type-check (Cannot find module 'node-cron') and integration tests can't run their migrations.Regenerated via
npm install— no dependency versions changed inpackage.json, this only adds the missing entries and their transitive deps.Verification
npx tsc --noEmit— clean (was failing on the missing module before this)One note for anyone running these locally: the lockfile now resolves
lru-cachev11 transitively, which needs Node ≥ 20.6 (diagnostics_channel.tracingChannel). CI is on Node 20 and fine; local Node 18 will fail in Jest's global setup.🤖 Generated with Claude Code