Skip to content

Sync package-lock.json so npm ci passes - #3

Merged
setnilson merged 1 commit into
masterfrom
fix/sync-package-lock
Aug 21, 2026
Merged

Sync package-lock.json so npm ci passes#3
setnilson merged 1 commit into
masterfrom
fix/sync-package-lock

Conversation

@setnilson

Copy link
Copy Markdown
Owner

What

Regenerates package-lock.json so it's in sync with the workspace package.jsons.

Why

The Typecheck & lint check on #2 failed at the npm ci step:

npm ci can only install when package.json and package-lock.json are in sync.
Missing: react@19.2.8, react-dom@19.2.8, @datadog/vite-plugin@3.2.12 from lock file

The newly-scaffolded app resolved newer versions than the committed lockfile carried (the lockfile had been left at react 19.2.3 / @datadog/vite-plugin 3.2.9-dev.0 from an earlier debugging pin). npm ci is strict, so it aborted before typecheck ran.

Fix

npm install to regenerate the lockfile. Verified locally: npm ci, npm run typecheck, and npm run lint all pass.

Note (follow-up, not this PR)

@datadog/vite-plugin is inconsistent across apps — apps/sarah-s-app-thu-… and the root pin 3.2.9-dev.0 (debugging leftover), while the other apps use ^3.2.1. Worth harmonizing to one range later.

The new app (sarah-s-app-fri) pulled react/react-dom 19.2.8 and
@datadog/vite-plugin 3.2.12, but the committed lockfile was left at older
versions (partly from an earlier vite-plugin pin), so `npm ci` failed with
"package.json and package-lock.json are not in sync" — which broke the
Typecheck & lint check before it could run. Regenerated the lockfile with
`npm install`; npm ci, typecheck, and lint all pass now.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@setnilson
setnilson merged commit 3e60757 into master Aug 21, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant