chore: bump esbuild from 0.19.x to 0.21.x #517
Merged
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
Why bump from 0.19.x: Plenty of bug fixes and performance improvements Why bump to 0.21.x and not 0.23.x: tsx, which I plan to propose soon, uses 0.21.x, so this will avoid duplicated dependencies.
You can use |
|
tsx is well-maintained. They are currently discussing a bump to 0.22.x: privatenumber/tsx#606. I don't believe there's an urgent need to override secondary dependencies tsx has been tested with. Especially when the change was done with intention of improving reliability :D |
merceyz
approved these changes
Jul 11, 2024
aduh95
approved these changes
Jul 12, 2024
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 bump from 0.19.x:
Plenty of bug fixes and performance improvements
Why bump to 0.21.x and not 0.23.x:
tsx, which I propose in #518, uses 0.21.x (at the moment of writing), so this will avoid duplicated dependencies. It's also easier to handle, and potentially roll back, major version bumps that were split into stages.