Bump @types/node from 25.9.4 to 26.0.0#297
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 25.9.4 to 26.0.0. - [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.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 50: The `@types/node` dependency has been updated to v26 which includes
breaking changes in crypto, fs, child_process, buffer, perf_hooks, util, and
worker_threads modules. Although the project's TypeScript version (^5.9.2) meets
the v26 requirement, verify type compatibility by running the type checking
commands (npm run lint and/or tsc) to ensure no new type errors are introduced
by this major version bump.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 4db404f5-2897-4376-afdf-e1986db671d5
📒 Files selected for processing (1)
package.json
| "@biomejs/biome": "^1.9.4", | ||
| "@lokalise/biome-config": "^2.0.0", | ||
| "@types/node": "^25.0.2", | ||
| "@types/node": "^26.0.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the breaking changes and type definition differences between @types/node v25 and v26?
💡 Result:
The update from @types/node v25 to v26, released in June 2026, introduces several breaking changes and cleanups designed to improve type accuracy and alignment with Node.js behavior [1][2][3]. Key breaking changes and updates include: TypeScript Compatibility: v26 requires TypeScript 5.6 or higher, as support for iterator helper compatibility definitions for older TS versions has been removed [1]. Crypto Library Cleanup: Massive refactoring was performed on the crypto library to correct input types [1]. - Many methods now exclusively accept canonicalized types (e.g., BinaryLike, KeyLike) rather than fragmented or inconsistent union types [1]. - The duplicate CipherKey interface has been deprecated in favor of KeyLike [1]. - Crypto-specific encoding unions have been replaced with the canonical BufferEncoding [1]. API Removals and Deprecations: - Orphaned interfaces previously marked as deprecated were removed from buffer, fs, perf_hooks, util, and worker_threads [1]. - module.register is deprecated in favor of registerHooks [4]. API Corrections and Adjustments: - Child Process: The exception behavior for exec and execFile has been corrected to provide a more consistent interface [1]. - Buffer Input: Type definitions for buffer inputs have been updated to strictly align with Node.js source requirements, with some methods specifically requiring ArrayBufferView or ArrayBufferLike instead of broader unions [1]. - Dependency Update: The undici-types dependency has been updated to v8.3.0 [1][2]. Note that DefinitelyTyped does not maintain a traditional changelog for @types/node releases, so developers migrating between major versions should review the specific Pull Request in the DefinitelyTyped repository (e.g., PR #75025) for detailed diffs and breaking changes [1][5].
Citations:
- 1: node: v26 DefinitelyTyped/DefinitelyTyped#75025
- 2: https://npmx.dev/diff/@types/node/v/22.19.17...26.0.0
- 3: https://npmx.dev/package/@types/node/v/26.0.0
- 4: node: v26 DefinitelyTyped/DefinitelyTyped#74983
- 5: Where do I find a changelog for this @types/node? DefinitelyTyped/DefinitelyTyped#52998
🏁 Script executed:
# Check TypeScript version in package.json
rg -A 2 -B 2 '"typescript"' package.json
# Check for usage of potentially affected modules
echo "=== Checking for crypto usage ==="
rg -i "require.*crypto|from.*['\"]crypto" --type ts --type js -c
echo "=== Checking for fs usage ==="
rg -i "require.*fs|from.*['\"]fs" --type ts --type js -c
echo "=== Checking for child_process usage ==="
rg -i "require.*child_process|from.*['\"]child_process" --type ts --type js -c
echo "=== Checking for buffer usage ==="
rg -i "require.*buffer|from.*['\"]buffer" --type ts --type js -c
echo "=== Checking for perf_hooks usage ==="
rg -i "require.*perf_hooks|from.*['\"]perf_hooks" --type ts --type js -c
echo "=== Checking for util usage ==="
rg -i "require.*util['\"]|from.*['\"]util['\"]" --type ts --type js -c
echo "=== Checking for worker_threads usage ==="
rg -i "require.*worker_threads|from.*['\"]worker_threads" --type ts --type js -cRepository: lokalise/node-core
Length of output: 449
@types/node v26 requires TypeScript 5.6+; verify type compatibility.
This major version bump (v25 → v26) includes breaking changes documented in DefinitelyTyped PR #75025, including crypto library refactoring, API removals, and type adjustments. However, the project's TypeScript version (^5.9.2) already exceeds the v26 requirement, and the codebase does not directly import the primarily affected modules (crypto, fs, child_process, buffer, perf_hooks, util, worker_threads).
Before merging, run type checking (npm run lint / tsc) to confirm no type errors are introduced.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 50, The `@types/node` dependency has been updated to v26
which includes breaking changes in crypto, fs, child_process, buffer,
perf_hooks, util, and worker_threads modules. Although the project's TypeScript
version (^5.9.2) meets the v26 requirement, verify type compatibility by running
the type checking commands (npm run lint and/or tsc) to ensure no new type
errors are introduced by this major version bump.
|
Superseded by #299. |
Bumps @types/node from 25.9.4 to 26.0.0.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)