update babel and forcibly set regenerator runtime version #194
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
|
Not rightly sure what's causing microbundle to not be found. this builds w/o issue locally.
Any chance you can rerun @DavidWells ? |
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 have set babel to the latest consistent version (7.14.5, 7.15.0 was partially built within the last few hours). This did not fix the issue in analytics.js regarding the use of regeneratorRuntime's Function() call. Explicitly setting the regeneratorRuntime in any package that has it forces for the updates that... should fix this.
This ties to #192, hopefully resolving it... but I don't want to commit to it. I'll keep plugging away.