Merged
Conversation
I used npm-check-update to generate this PR: 1. npx npm-check-updates -u 2. npm install
kripken
approved these changes
Apr 9, 2026
mymindstorm
reviewed
Apr 10, 2026
Collaborator
mymindstorm
left a comment
mymindstorm
left a comment
There was a problem hiding this comment.
We actually don’t want to update @types/node to 25. Our runtime is node24. types/node’s version is supposed to directly correspond to the version of node in use at runtime. The version string from before should be picking up minor and patch releases, so at most this would need an update to the lock file but not package.json.
Line 30 in 54cd688
Collaborator
Author
|
Oops. will revert. |
sbc100
added a commit
that referenced
this pull request
Apr 10, 2026
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
3 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.
I used npm-check-update to generate this PR: