chore(deps-dev): bump @types/node from 22.19.21 to 26.0.0

[dependabot]

Bumps @types/node from 22.19.21 to 26.0.0.

Commits

• See full diff in compare view

[cloudflare-workers-and-pages]

Deploying agent-render with    Cloudflare Pages

Latest commit:	4569994
Status:	✅  Deploy successful!
Preview URL:	https://43469c31.agent-render.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-type-7pfi.agent-render.pages.dev

View logs

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​node@​22.19.21 ⏵ 26.0.0

View full report

[greptile-apps]

Greptile Summary

This PR is a Dependabot-automated bump of @types/node from 22.19.21 to 26.0.0, which also pulls in undici-types 8.3.0 (from 6.21.0) as a transitive dependency. The rest of the lockfile changes are npm bookkeeping (peer flag reorganization) with no functional effect.

• @types/node major version jump: Type definitions advance from Node 22 to Node 26 while the project's engines.node >= 20.10.0 constraint stays at Node 20. TypeScript will now silently accept Node-26-only API calls that would fail at runtime on the minimum supported Node version.
• undici-types co-bump: 8.3.0 ships alongside @types/node@26 and replaces 6.21.0; no independent action is required.
• Lockfile peer flag churn: Dozens of packages gained or lost the peer flag — this is a consequence of npm re-classifying peer relationships after the resolution change and does not affect installed packages.

Confidence Score: 4/5

Safe to merge only if the deployed Node version is 26; risky if the project actually runs on Node 20 or 22 as declared in engines.

The type definitions now describe a Node version four majors ahead of the declared minimum runtime. Any Node 26-only API used in source code will pass tsc --noEmit but throw at runtime on Node 20/22, silently removing a correctness guarantee that the typecheck CI step is supposed to provide.

package.json — the engines.node constraint and the @types/node major should agree; currently they are four major versions apart.

Important Files Changed

Filename	Overview
package.json	Bumps @types/node from ^22.19.21 to ^26.0.0; engines.node stays at >=20.10.0, creating a mismatch where tsc accepts Node 26-only APIs that would fail on the declared minimum runtime.
package-lock.json	Lockfile regenerated to reflect the @types/node and undici-types version changes; peer-flag reorganization across many packages is expected npm bookkeeping with no functional impact.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["engines.node >= 20.10.0\n(runtime target)"] -->|"gap: Node 20/21/22/23/24/25"| B["@types/node@26\n(type-check layer)"]
    B --> C["tsc --noEmit passes\nfor Node 26-only APIs"]
    C -->|"deployed on Node 20"| D["💥 Runtime Error\n(API not available)"]
    B --> E["undici-types@8.3.0\n(transitive dep)"]
    style D fill:#ff6b6b,color:#fff
    style B fill:#ffd93d
    style A fill:#6bcb77

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["engines.node >= 20.10.0\n(runtime target)"] -->|"gap: Node 20/21/22/23/24/25"| B["@types/node@26\n(type-check layer)"]
    B --> C["tsc --noEmit passes\nfor Node 26-only APIs"]
    C -->|"deployed on Node 20"| D["💥 Runtime Error\n(API not available)"]
    B --> E["undici-types@8.3.0\n(transitive dep)"]
    style D fill:#ff6b6b,color:#fff
    style B fill:#ffd93d
    style A fill:#6bcb77

Loading

_{Reviews (2): Last reviewed commit: "chore(deps-dev): bump @types/node from 2..." | Re-trigger Greptile}

[kilo-code-bot]

SUGGESTION: @types/node is bumped across 4 major versions (22 -> 26).

@types/node@26 ships types for Node 26, but package.json declares engines.node >= 20.10.0. Using Node 26 types against a Node 20 runtime baseline can let Node 22+/26-only APIs typecheck cleanly while being unavailable at runtime. The prior ^22 pin was already ahead of the engine floor, so this widens that gap. Confirm the CI typecheck (tsc --noEmit via npm run test:ci / check) passes green before merging.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
package.json	80	@types/node bumped 4 majors (22 -> 26), ahead of engines.node >= 20.10.0 runtime target; confirm CI tsc --noEmit passes

Files Reviewed (2 files)

• package.json - 1 issue (existing inline comment)
• package-lock.json - lock file (generated, no reviewable issues)

Fix these issues in Kilo Cloud

Previous Review Summary (commit e79055f)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit e79055f)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
package.json	85	@types/node bumped 4 majors (22 -> 26), ahead of engines.node >= 20.10.0 runtime target; confirm CI tsc --noEmit passes

Files Reviewed (2 files)

• package.json - 1 issue
• package-lock.json - lock file (generated, no reviewable issues)

Fix these issues in Kilo Cloud

---

_{Reviewed by GLM-5.2 · Input: 68.2K · Output: 6.6K · Cached: 79.9K}

[baanish]

Superseded by #79, which bumps this dependency (and the rest of the safe batch) together and is merged into main. react/react-dom were bumped in lockstep there to satisfy the peer constraint that broke #78 alone.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.