Repository navigation
chore(deps): upgrade @types/node to v26 - #188
Merged
Merged
Conversation
Major version bump (24.13.6 -> 26.6.2), the second of the deps held back from #186. @types/node's major version tracks the Node.js release it types, not this project's actual runtime (pinned to Node >=24 <25 in package.json engines) — the version skew is type-only and additive, so it doesn't change what Node APIs are actually callable at runtime. typecheck, lint, build, and the full vitest suite (355/355) all pass unchanged. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CxiGnVuEYfy8n8i6Pano5x
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
2 participants
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.
Summary
Second of the three major-version upgrades held back from #186 (after #187's
lucide-reactv1 bump).@types/node24.13.6 → 26.6.2 (major).@types/node's major version tracks the Node.js release its type definitions describe, not necessarily the runtime a project actually uses. This repo'spackage.jsonenginesstill pins Node>=24 <25; the newer type definitions are additive (types for newer Node APIs), so this doesn't change what's actually callable at runtime on Node 24, and no type errors surfaced from the bump.Test plan
npm run typecheck— passesnpm run lint— passesnpm run build— passes (pre-existing >500kB chunk-size warning, unrelated)npm test(vitest) — 355/355 tests pass, 41/41 files🤖 Generated with Claude Code
https://claude.ai/code/session_01CxiGnVuEYfy8n8i6Pano5x
Generated by Claude Code