fix: upgrade TypeScript to 5.2 to resolve @types/node ffi.d.ts syntax errors#355
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job ci
fix: upgrade TypeScript to 5.2 to resolve @types/node ffi.d.ts syntax errors
Jul 21, 2026
… CI rendering differences
huaxiabuluo
marked this pull request as ready for review
July 22, 2026 06:28
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
@types/node(transitive dependency) uses theusing/await usingexplicit resource management syntax introduced in TypeScript 5.2. TypeScript 4.x cannot parse this syntax — even withskipLibCheck: true— causing 50 syntax errors and a build failure infather build/gulp-typescript.Change
typescriptindevDependenciesfrom^4.1.3→^5.2.0TypeScript 5.x is backward compatible with the existing source.
@typescript-eslint@5.x(used for linting) supports TypeScript up to 5.4.x, so no ESLint changes are needed.