Upgrade @babel/* packages to last version #5305
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
This should fix grommet#5303
jcfilben
approved these changes
Jun 9, 2021
ShimiSun
approved these changes
Jun 10, 2021
|
Deployment seems to work as expected, thank you for your contribution! 💟 |
|
Did you have any plan on when a new release will be made? I'm waiting this commit to finish my conversion CRA to vitejs 😄 |
|
Since there was already a release done this month there probably won't be another one until sometime next month. In the meantime you can use the stable branch to access changes that are on the master branch but haven't been released yet https://github.com/grommet/grommet/wiki/What-is-grommet-stable-and-how-to-use-it%3F |
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.
What does this PR do?
This PR upgrade babel packages. This should allow user to use grommet with vitejs.
What testing has been done on this PR?
None
Any background context you want to provide?
vitejs/vite#3437
What are the relevant issues?
#5303
Should this PR be mentioned in the release notes?
Is this change backwards compatible or is it a breaking change?
It should be backward compatible.