Skip to content

build: regenerate package-lock.json to match workspace dependencies - #1713

Merged
mbouaziz merged 1 commit into
mainfrom
fix/sync-package-lock
Nov 19, 2026
Merged

mbouaziz merged 1 commit into
mainfrom
fix/sync-package-lock

Conversation

@mbouaziz

@mbouaziz mbouaziz commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Regenerates the root package-lock.json so it satisfies all workspace package.json files. This un-breaks the docs workflow's build job, which has been red on main and on PRs since the dependabot bumps below landed.

Root cause

Dependabot commits bumped dependency ranges in workspace examples without a matching root lock update:

  • examples/cache_invalidation/edge_service/package.json: @types/node ^26.6.6, typescript ^6.0.3, eslint 10.15.0 (e607811 and follow-ups)
  • examples/blogger/reactive_service/package.json: similar bumps

The root lock still pinned @types/node 20.19.9 / typescript 5.9.3 under those workspaces, so npm ci at the repo root fails with:

npm error code EUSAGE
`npm ci` can only install packages when your package.json and package-lock.json are in sync.
Invalid: lock file's @types/node@20.19.9 does not satisfy @types/node@26.6.6
Missing: eslint@10.15.0 from lock file
...

The docs workflow runs root npm ci on PRs touching www/**, skipruntime-ts/**/src/**, or skiplang/**/ts/**/src/** — which is why #1711 (touching skiplang/prelude/ts/wasm/src/sk_runtime.ts) showed a red build check even though its CircleCI checks were all green and it merged (docs is not a required check; required checks are the CircleCI contexts only).

Fix

npm install --package-lock-only --ignore-scripts at the root. Only package-lock.json changed (+919/-162): nested entries for the bumped example workspaces, e.g. examples/cache_invalidation/edge_service/node_modules/@types/node now 26.6.6. The lock's top-level metadata (name: "skip", lockfileVersion: 3) is unchanged — regenerated in a directory whose name differs from the repo root, so the name field was explicitly restored.

Validation

  • On unmodified main (4b3ad39): npm ci --ignore-scripts --no-audit --no-fund --dry-run fails with the EUSAGE above.
  • On this branch: the same command exits 0; npm ci --no-audit --no-fund --dry-run in www/ (separate lock) also exits 0.
  • End-to-end: triggered the docs workflow on this branch via workflow_dispatch — the build job (root npm ci, TS package builds, docusaurus site build) completed success (run 44440100236; the deploy job fails on manual runs since Pages isn't configured for workflow_dispatch, which is expected and unrelated).

AI assistance: prepared with Mistral Vibe; the commit carries a Co-Authored-By trailer.

Dependabot bumps in examples/cache_invalidation/edge_service and
examples/blogger/reactive_service raised @types/node/typescript/eslint
ranges without a matching root lock update, so `npm ci` at the repo root
fails with EUSAGE and the docs workflow's build job is red on main and on
every PR touching skiplang/**/ts/**/src/** (e.g. #1711).

Regenerated with `npm install --package-lock-only`. Validated with
`npm ci --ignore-scripts --no-audit --no-fund --dry-run` at the root
(passes now, EUSAGE on unmodified main) and `npm ci --dry-run` in www/.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
@mbouaziz
mbouaziz force-pushed the fix/sync-package-lock branch from f80aaf7 to fc97f62 Compare November 19, 2026 01:57
@mbouaziz
mbouaziz merged commit e9300df into main Nov 19, 2026
9 of 10 checks passed
@mbouaziz
mbouaziz deleted the fix/sync-package-lock branch November 19, 2026 03:09

This branch had an error being deployed

1 failed deployment
github-pages — fc97f626 Deployed Nov 19, 2026 by mbouaziz via deploy #76
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