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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: The documentation for babel-plugin-polyfill-corejs3 seems to have an error description? #164
Comments
Hey @limingcan562! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite. |
馃捇
How are you using Babel?
babel-loader (webpack)
Input code
Configuration file name
No response
Configuration
Current and expected behavior
When the value of version is the latest
version
ofcore-js
(require("core-js/package.json").version
), the compiled code is injected with224 lines
.When I change the version to
3.20
, the compiled code is injected with208 lines
.Hello, I am migrating from the old configuration method to the new one.
I see from the documentation
that version only works if you use
"method": "usage-global"
or"method": "usage-pure"
.But when I changed the value of version, I found that it worked. So the version configuration item also acts on
"method": "entry-global"
?Environment
System:
OS: macOS 12.2.1
Binaries:
Node: 14.18.1 - /usr/local/bin/node
npm: 6.14.15 - /usr/local/bin/npm
npmPackages:
@babel/cli: ^7.21.0 => 7.21.0
@babel/core: ^7.21.4 => 7.21.4
@babel/plugin-transform-runtime: ^7.21.4 => 7.21.4
@babel/preset-env: ^7.21.4 => 7.21.4
@babel/runtime-corejs3: ^7.21.5 => 7.21.5
babel-loader: ^9.1.2 => 9.1.2
babel-plugin-polyfill-es-shims: ^0.8.0 => 0.8.0
babel-plugin-polyfill-regenerator: ^0.4.1 => 0.4.1
webpack: ^5.81.0 => 5.81.0
Possible solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: