Skip to content

chore(deps-dev): bump @types/node from 20.19.39 to 26.6.5 - #62

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.6.5
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.6.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @types/node from 20.19.39 to 26.6.5.

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 22, 2026
@hansi-codes

hansi-codes Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

A clean npm ci fails because the updated lockfile omits Nitro’s lru-cache peer package.

This PR updates the project’s Node.js type declarations to the v26 series and updates the associated undici-types dependency. The manifest and lockfile are changed to reflect the new versions.

Verdict New comments Fixed Still open
🛑 Changes requested 1 0 0
Finding Where
🟠 lru-cache: clean npm ci fails with the updated lockfile package-lock.json:1962
Fix with agent prompt
### Issue 1
package-lock.json:1962
**lru-cache: clean npm ci fails with the updated lockfile**

The lockfile now omits `node_modules/nitro/node_modules/lru-cache@11.5.3`, which `unstorage` declares as an optional peer. Running `npm ci` with Node 22.23.4/npm 10.9.9 fails with `Missing: lru-cache@11.5.3 from lock file`, so clean installs cannot proceed with this lockfile.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 2
File Change
package.json Bumps the development dependency on @types/node.
package-lock.json Updates @types/node and undici-types and removes Nitro's nested lru-cache entry.

Reviewed 9708bbd · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.

@hansi-codes hansi-codes Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Tier S · Looks good to merge. Summary

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.19.39 to 26.6.5.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.6.5
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/types/node-26.6.5 branch from f83b820 to 9708bbd Compare November 2, 2026 10:24

@hansi-codes hansi-codes Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 1 blocking finding to address. Summary

Comment thread package-lock.json
"node": "20 || >=22"
}
},
"node_modules/nitro/node_modules/unstorage": {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lru-cache: clean npm ci fails with the updated lockfile

The lockfile now omits node_modules/nitro/node_modules/lru-cache@11.5.3, which unstorage declares as an optional peer. Running npm ci with Node 22.23.4/npm 10.9.9 fails with Missing: lru-cache@11.5.3 from lock file, so clean installs cannot proceed with this lockfile.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package-lock.json
Line: 1962

Comment:
**lru-cache: clean npm ci fails with the updated lockfile**

The lockfile now omits `node_modules/nitro/node_modules/lru-cache@11.5.3`, which `unstorage` declares as an optional peer. Running `npm ci` with Node 22.23.4/npm 10.9.9 fails with `Missing: lru-cache@11.5.3 from lock file`, so clean installs cannot proceed with this lockfile.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants