Skip to content

chore: regenerate package-lock.json for Node 26 engines - #119

Open
kkuffour wants to merge 1 commit into
feat/ess-3-token-exchange-implementationfrom
chore/regen-lockfile-node-26
Open

kkuffour wants to merge 1 commit into
feat/ess-3-token-exchange-implementationfrom
chore/regen-lockfile-node-26

Conversation

@kkuffour

@kkuffour kkuffour commented Nov 16, 2026 •

Copy link
Copy Markdown

First PR into the feat/ess-3-token-exchange-implementation integration branch (ESS 3 support while keeping CSS and solidcommunity.net working). This one is housekeeping only.

What

#118 changed package.json engines.node to "26.x" but didn't regenerate the lockfile, which still says ">=24.x". Running a plain npm install brings them back in sync:

  • root engines.node: ">=24.x" → "26.x"
  • drops 17 stale "peer": true flags that current npm no longer writes

No dependency versions, resolved URLs or integrity hashes change.

Why a separate PR

It's kept apart from the test-runner/CI PR that follows, so the lockfile fix stays its own commit when PRs into the integration branch are squash-merged.

Checked

  • npm ci --dry-run succeeds, and a second npm install leaves the file unchanged.
  • npm install --package-lock-only was deliberately not used: it also records bundled files of an optional Tailwind wasm package (@tailwindcss/oxide-wasm32-wasi), which a normal install omits. That's noise, not a real change.
  • Independent review of the diff: no findings.

The Node 26 LTS change (fb5cdb2) updated package.json engines to
"26.x" but did not regenerate the lockfile, which still recorded
">=24.x". Running `npm install` brings it back in sync:

- root "engines.node": ">=24.x" -> "26.x"
- drops 17 stale "peer": true flags that current npm no longer writes

No dependency versions change. `npm ci` succeeds against the result.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
solid-file-manager Ready Ready Preview Nov 16, 2026 3:57pm UTC

This branch was successfully deployed

1 active deployment
Preview — 1b4ca70d Deployed Nov 16, 2026 by vercel[bot]
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