Fix: Running the customized example results in an error #1445
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
tonyjmartinez
changed the title
|
I found that the same issue was happening in a few of the other examples so I went a similar route. I didn't upgrade in examples where the upgrade introduced a different problem. |
…didn't work so I had to downgrade
sapegin
requested changes
Oct 14, 2019
|
Hey @sapegin, |
|
@elevatebart Yup, looks good now! |
|
🎉 This PR is included in version 10.4.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Apr 7, 2022
Open
Open
Open
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.
I encountered the following error running the customized example.
Upgrading the packages in package.json fixed that problem. Updating the babel config fixed a problem that the package upgrade introduced with core-js.