Gathering detailed insights and metrics for babel-plugin-polyfill-corejs3
Gathering detailed insights and metrics for babel-plugin-polyfill-corejs3
A set of Babel plugins that enable injecting different polyfills with different strategies in your compiled code.
npm install babel-plugin-polyfill-corejs3
Typescript
Module System
Node Version
NPM Version
91.6
Supply Chain
86.5
Quality
85.6
Maintenance
100
Vulnerability
99.3
License
TypeScript (65.83%)
JavaScript (34.17%)
Total Downloads
3,958,678,703
Last Day
4,649,432
Last Week
20,807,898
Last Month
94,034,924
Last Year
1,271,586,101
341 Stars
409 Commits
59 Forks
18 Watching
4 Branches
49 Contributors
Minified
Minified + Gzipped
Latest Version
0.11.1
Package Id
babel-plugin-polyfill-corejs3@0.11.1
Unpacked Size
216.05 kB
Size
48.72 kB
File Count
15
NPM Version
lerna/3.22.0/node@v23.5.0+x64 (linux)
Node Version
23.5.0
Publised On
24 Jan 2025
Cumulative downloads
Total Downloads
Last day
-6.3%
4,649,432
Compared to previous day
Last week
-16.4%
20,807,898
Compared to previous week
Last month
3.2%
94,034,924
Compared to previous month
Last year
4.8%
1,271,586,101
Compared to previous year
2
1
11
Using npm:
1npm install --save-dev babel-plugin-polyfill-corejs3
or using yarn:
1yarn add babel-plugin-polyfill-corejs3 --dev
Add this plugin to your Babel configuration:
1{ 2 "plugins": [["polyfill-corejs3", { "method": "usage-global", "version": "3.20" }]] 3}
This package supports the usage-pure
, usage-global
, and entry-global
methods.
When entry-global
is used, it replaces imports to core-js
.
See here for a list of options supported by every polyfill provider.
version
string
, defaults to "3.0"
.
This option only has an effect when used alongside "method": "usage-global"
or "method": "usage-pure"
. It is recommended to specify the minor version you are using as core-js@3.0
may not include polyfills for the latest features. If you are bundling an app, you can provide the version directly from your node modules:
1{ 2 plugins: [ 3 ["polyfill-corejs3", { 4 "method": "usage-pure", 5 // use `core-js/package.json` if you are using `usage-global` 6 "version": require("core-js-pure/package.json").version 7 }] 8 ] 9}
If you are a library author, specify a reasonably modern core-js
version in your
package.json
and provide the plugin the minimal supported version.
1{ 2 "dependencies": { 3 "core-js": "^3.20.0" 4 } 5}
1{ 2 plugins: [ 3 ["polyfill-corejs3", { 4 "method": "usage-global", 5 // improvise if you have more complicated version spec, e.g. > 3.1.4 6 "version": require("./package.json").dependencies["core-js"] 7 }] 8 ] 9}
proposals
boolean
, defaults to false
.
This option only has an effect when used alongside "method": "usage-global"
or "method": "usage-pure"
. When proposals
are true
, any ES proposal supported by core-js will be polyfilled as well.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
Found 13/30 approved changesets -- score normalized to 4
Reason
3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
56 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More