update dependencies #406
Merged
update dependencies #406
Conversation
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
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.
Why
Maintenance
How
Update dependencies
Test with node 18, 20, 22 instead of 16, 18, 20
Some of the dependencies I updated require Node 18 as a minimum target, but this should be fine because Node 16 has been unmaintained for ~1 year so we don't need to worry about supporting it anymore. We are running Node 18 as default on EAS Build and our services are launched using Node 18. I also believe we can drop Node 16 support in EAS CLI.
Test Plan
Tests