Repository navigation
build(web): upgrade to Node 26 LTS and TypeScript 7 - #939
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 frontend toolchain now uses Node 26.13.0 LTS and TypeScript 7.0.2 for typechecking. Align Node engine requirements, typings, CI, Docker build defaults, and developer documentation, and update Preact to 11.2.0 and Babel core to 8.1.0.
TypeScript 7 runs through the official
@typescript/nativealias, alongside the TypeScript 6 compatibility API required by ESLint. Root TypeScript stays on 5.9.3 to satisfy the OpenAPI generator's compiler API and peer dependency. Contract declaration tests exercise the root compiler and the frontend's native compiler. Normalize MQTT test socket data to buffers for the Node 26 typings.Validation on Node 26.13.0:
npm ciinstalls for the root and frontend.Full Docker builds and browser E2E tests were not run. Existing Jest development dependency advisories remain (17 moderate, 1 low); this upgrade does not resolve them.