-
-
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
Direct usage of core-js-compat
#1604
Comments
I don't believe use core-js-compat as a dependency would be a good idea -- it would cause much trouble in wasm. However, I believe it's good to include_str core-js-compat directly since it will always reside in node_modules/core-js-compat. @kdy1 what's your opinion? |
@Austaras I think you are right, it will make updating much easier. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
As I could see, copy of
core-js-compat
data used inswc
version ofpreset-env
is critically obsolete - 1.5 year. Each new version ofcore-js-compat
contains updates engines support data,core-js-compat
contains information about new modules and entry points. Without this information impossible to use it correctly - new modules will not be injected even if they are required.Compat data should be updated even without
swc
updates for making possible to use actualcore-js
versions properly, so the only way to do it - usage ofcore-js-compat
as a dependency.The text was updated successfully, but these errors were encountered: