chore: sync package-lock with declared dependencies #18

Merged
bermudalamb merged 2 commits from chore/sync-package-lock into main 2026-08-14 17:58:22 -05:00
Owner

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

`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)
bermudalamb added 1 commit 2026-08-14 17:21:58 -05:00
chore: sync package-lock with declared dependencies
SonarQube Analysis / sonarqube (pull_request) Successful in 5m9s
Tests / backend-unit (pull_request) Successful in 1m6s
Tests / backend-integration (pull_request) Successful in 2m24s
Tests / frontend-e2e (pull_request) Failing after 54s
26363ab13f
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>
bermudalamb added 1 commit 2026-08-14 17:58:00 -05:00
Merge branch 'main' into chore/sync-package-lock
SonarQube Analysis / sonarqube (pull_request) Successful in 6m34s
Tests / backend-unit (pull_request) Successful in 1m37s
Tests / backend-integration (pull_request) Successful in 3m26s
Tests / frontend-e2e (pull_request) Failing after 52s
2c7ae7517e
bermudalamb merged commit 0935bc14f1 into main 2026-08-14 17:58:22 -05:00
bermudalamb deleted branch chore/sync-package-lock 2026-08-14 17:58:38 -05:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bermudalamb/redefined-designs#18