bump esbuild version to 0.18
#7830
Closed
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
🦋 Changeset detectedLatest commit: cf80ebf The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
the
pkg: astro
mayank99
changed the title
esbuild version to 0.18.x.esbuild version to 0.18
|
not sure why test is failing looks unrelated to esbuild |
Ah we've had some weird problems with this one before. I can take a look. Thanks for the PR! |
|
Closing because esbuild 0.19 is already out. Hopefully astro will bump at some point |
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.
Changes
updated
astro > esbuildfrom 0.17 to 0.18vite 4.4 uses esbuild 0.18, so installing astro was resulting in two versions of esbuild inside node_modules.
i believe no code changes are necessary as they were already handled in #7479/#7746
Testing
N/A. no code changes.
Docs
N/A. no code changes.