refactor: Bump @types/node from 25.6.0 to 26.1.1

[mtrezza]

Closes #907

Changes

Bumps the direct devDependency @types/node from 25.6.0 to 26.1.1 (major version bump, 25 -> 26). This package provides TypeScript type definitions for Node.js and has no runtime footprint. Its transitive dependency undici-types updates accordingly (~7.19.0 -> ~8.3.0).

Breaking Changes

None affecting this repository. @types/node is type-definitions-only, so a major bump can only break the build via changed/removed type definitions referenced by the project's own code. The project type-checks cleanly with the new version:

• npx tsc --noEmit produces identical output before and after the bump (one pre-existing, unrelated TS5107 moduleResolution deprecation notice in tsconfig.json; no new errors).
• tsconfig.json sets skipLibCheck: true, so declaration files are not deeply type-checked.
• The bump replaces the previous @types/node major (Node 25 typings) with Node 26 typings; the repo's engines still target Node 18/20/22 and this is unaffected since these are types only.

Code Changes

None. Only package.json and package-lock.json are modified; the lockfile diff is confined to @types/node and its transitive undici-types.

Summary by CodeRabbit

• Chores
  • Updated Node.js type definitions to the latest version.
  • Refreshed related dependency metadata for improved compatibility.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f0549dd8-ef78-410f-9c24-1208d3e79ec3

📥 Commits

Reviewing files that changed from the base of the PR and between 07307e3 and 30956d8.

📒 Files selected for processing (2)

• package-lock.json
• package.json

---

📝 Walkthrough

Walkthrough

The development dependency @types/node is upgraded from 25.6.0 to 26.1.1. The lockfile updates its resolved metadata and changes the associated undici-types dependency from 7.19.2 to 8.3.0.

Changes

Node type definitions update

Layer / File(s)	Summary
Update Node type dependencies package.json, package-lock.json	@types/node is upgraded to 26.1.1, while lockfile metadata and undici-types are updated to 8.3.0 with matching requirements, URLs, and integrity hashes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	Repo diff only shows a dependency bump; no review comments or discussion artifacts are available to verify feedback engagement.	Provide PR review-thread evidence showing the user discussed feedback and either implemented it in a commit or got the reviewer to retract it.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the dependency bump and uses an allowed prefix.
Linked Issues check	✅ Passed	The PR directly fulfills issue #907 by bumping @types/node from 25.6.0 to 26.1.1.
Out of Scope Changes check	✅ Passed	The changes stay within scope, affecting only package.json and package-lock.json for the dependency update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	PASS: Only @types/node/undici-types version bumps in package.json/lockfile; no source code or scripts changed, and no package-specific security advisories surfaced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}