Repository navigation
Update development dependencies and Node.js to 26.12.1 - #19
Merged
Merged
Conversation
ConsoleTVs
marked this pull request as ready for review
October 24, 2026 13:04
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
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
Update every compatible development dependency and regenerate the lockfile. Preserve published Node/framework peer requirements; only the contributor toolchain minimum changes.
Keep Vitest 4's mock-clearing behavior explicitly: Vitest 5's new global clearing default resets mocks belonging to active concurrent sibling tests. Scope new React globals/immutability rule exceptions to test fixtures, with one targeted negative-hook-fixture exception. Production React rules remain enabled. Use an explicit config import extension for Vite's native loader.
Evidence
After: Clean
npm ci, 113 tests pass, coverage passes,npm auditreports zero vulnerabilities, and the dependency tree has no invalid peers. Registry comparison shows TypeScript is the only dev dependency not at its latest stable release.<7peer constraints still produce an invalid dependency tree. Retain supported TypeScript 6 rather than force incompatible peers; rationale is documented in AGENTS.md.Merge Danger
Door: two-way
Blast Radius: tooling
Contributors and CI require Node 26.12.1+. Published runtime engines and framework peer ranges are unchanged. New major versions of Babel/Vitest are covered by builds, runtime export smoke checks, and the complete test suite. No ticket.