Added an option to enable polyfill for Babel Transform Runtime plugin #262
Conversation
This file contains hidden or 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
|
Thanks for this PR! I'm trying to reduce the amount of I will be working on a way of extending the configuration, described in #265 #280 Please let me know if it sounds like a viable solution to your problem and would make you consider using it. |
|
I agree that this is not best approach, so I'm happy about this decision. |
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.
Hi,
I've added an option with docs update to enable polyfill in Babel Transform Runtime plugin.
This option is recommended for libraries, while babel-polyfill is recommended for apps, but because I'm building an app that's embeddable on arbitrary websites, global polluting polyfill is not an option and so I cannot use babel-polyfill.