fix: update @types/node and ts-node for Node 22 compatibility#737
Merged
yogeshchoudhary147 merged 1 commit intomainfrom Dec 22, 2025
Merged
Conversation
- Update @types/node from ^12.19.8 to ^22.10.0 - Update ts-node from ~8.10.2 to ^10.9.2 - Regenerate package-lock.json to resolve nested dependency conflicts This fixes npm dependency resolution issues that were causing all Dependabot PRs to fail with lock file sync errors.
gyaneshgouraw-okta
approved these changes
Dec 22, 2025
yogeshchoudhary147
deleted the
fix/update-node-types-for-node22-compatibility
branch
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
2 participants
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.
Fixes dependency resolution issues causing Dependabot PRs to fail.
Changes:
@types/nodefrom ^12.19.8 to ^22.10.0ts-nodefrom ~8.10.2 to ^10.9.2package-lock.jsonWhy:
All Dependabot PRs (#725, #728, #734, #735, etc.) were failing because npm's resolver was pruning nested optional peer dependencies due to version conflicts between outdated base dependencies and what the build tools actually needed.