-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add node v22 and npm v10 support #2695
Open
mvadari
wants to merge
21
commits into
main
Choose a base branch
from
node-22
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 18 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
0974c3a
add node 22 support
mvadari ed5b400
add debug stuff
mvadari ad29606
try upgrading npm
mvadari cea1812
remove node 16
mvadari 709f71f
debug
mvadari 614485a
Merge branch 'main' into node-22
mvadari 7e6df39
remove tmux
mvadari 210fc84
Merge branch 'main' into node-22
mvadari 76d3cdf
only allow 22.9 onwards
mvadari c8ecaf7
Merge branch 'main' into node-22
mvadari 7cff723
try 22.8
mvadari 942243d
try 22.7
mvadari 20117c9
test more 22.x versions
mvadari 26928c5
test more versions
mvadari 5aafe0b
switch back to 22.x, clean up
mvadari 6995f3e
update README
mvadari 900590a
Merge branch 'main' into node-22
mvadari dc6010d
Merge branch 'main' into node-22
mvadari 18c7ff9
Merge branch 'main' into node-22
mvadari 2136820
Merge branch 'main' into node-22
mvadari bdb0ac8
Merge branch 'main' into node-22
mvadari File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,6 +65,6 @@ | |
], | ||
"engines": { | ||
"node": ">=18.0.0", | ||
"npm": ">=7.10.0 < 10.0.0" | ||
"npm": ">=7.10.0" | ||
} | ||
} |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the CI adhere to the minimum supported version of
npm
? If users who usenpm@v7
experience any problems with xrpl.js, we won't detect it since we are upgrading tonpm@v10
.