Repository navigation
Conversation
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>
kkuffour
requested review from
PreciousOritsedere,
hkir-dev,
jeswr,
langsamu and
matthieubosquet
as code owners
November 16, 2026 15:56
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First PR into the
feat/ess-3-token-exchange-implementationintegration branch (ESS 3 support while keeping CSS and solidcommunity.net working). This one is housekeeping only.What
#118 changed
package.jsonengines.nodeto"26.x"but didn't regenerate the lockfile, which still says">=24.x". Running a plainnpm installbrings them back in sync:engines.node:">=24.x"→"26.x""peer": trueflags that current npm no longer writesNo 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-runsucceeds, and a secondnpm installleaves the file unchanged.npm install --package-lock-onlywas 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.