-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider Ponyfill with core-js-pure
instead of core-js
to avoid pollute global environment.
#5584
Comments
Your link to babel is something completely different, and I think this is a huge security risk |
Sorry I misread it |
Note that the pure version / runtime transform has many limitations and many features are not available. However, it's the best option, for example, for libraries that should not pollute the global namespace.
|
Hey wanted to mention that this would be an important feature to use swc to build libraries. It's sort of fine to pollute the global scope when you're using SWC to build your app, but when building a library that someone uses in their app, it feels like a bad idea. (or am I being too cautious here?) |
Don't leave comments like +1 |
Describe the feature
Could be
Babel plugin or link to the feature description
https://babeljs.io/docs/en/babel-plugin-transform-runtime#core-js-aliasing
Additional context
https://ponyfoo.com/articles/polyfills-or-ponyfills
https://github.com/zloirock/core-js/blob/master/README.md
it could be enable when
corejs@3
andusage
The text was updated successfully, but these errors were encountered: