Upgrade TypeScript to 5.9.2, @types/node to 22.17.0, and webpack to 5.101.1 #961
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.
This PR upgrades key development dependencies to their latest compatible versions to improve type safety, leverage newer language features, and benefit from bug fixes and performance improvements.
Changes Made
Dependency Upgrades
5.1.3
→5.9.2
- Latest stable version with improved type checking and performance16.18.36
→22.17.0
- Updated Node.js type definitions for better compatibility5.77.0
→5.101.1
- Latest version with security fixes and performance improvementsAdditional Type Compatibility Fixes
4.0.6
→4.0.17
- Updated for better TypeScript 5.9 compatibility2.0.12
- Resolved transitive dependency type conflicts4.0.3
- Fixed FSWatcher interface compatibility issuesCode Fixes Required by Upgrades
Fixed TypeScript 5.9 stricter null checking:
Fixed regex compatibility for ES6 target:
Validation
✅ Build: TypeScript compilation succeeds without errors
✅ Lint: ESLint passes (minor warning about TypeScript version in plugin, but functionality works)
✅ Webpack: Production build completes successfully
✅ Main.js: Remains clean with no build artifacts
✅ Type Safety: All type issues resolved without using
skipLibCheck
The project now benefits from the latest TypeScript features, improved type checking, and updated security patches while maintaining full backward compatibility.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.