Repository navigation
chore: update Node.js to 26 LTS and refresh dependencies - #50
Merged
Merged
Conversation
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.
The project still targeted Node.js 24 and had outdated dependencies. Move the runtime and all three CI workflows to Node.js 26 LTS (validated on 26.13.0), update Node types to 26.6.6, Babylon.js to 9.33.1, and pnpm to 12.16.1, and refresh the dependency lockfile through Vite+.
Six focused commits keep the runtime, dependency refresh, each CI workflow, and README update separate.
Proof: frozen install, formatting/lint/types, root and workspace unit tests, all builds and bundle budgets, asset provenance, production audit, 74 desktop/mobile browser tests, and desktop/mobile Lighthouse passed. No outdated direct dependencies remain; Lighthouse retains advisory warnings.
Reviewed with sol-loop: 1 round with gpt-6.1-sol. Sol verdict: approved on high effort, no findings.
Created with gpt-6.1-sol in T3 Code (Codex harness).