Gathering detailed insights and metrics for ember-cli-babel-polyfills
Gathering detailed insights and metrics for ember-cli-babel-polyfills
Gathering detailed insights and metrics for ember-cli-babel-polyfills
Gathering detailed insights and metrics for ember-cli-babel-polyfills
Split-build polyfills for evergreen and legacy browsers
npm install ember-cli-babel-polyfills
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (89.85%)
HTML (10.15%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
33 Stars
29 Commits
6 Forks
2 Watchers
1 Branches
19 Contributors
Updated on Mar 03, 2025
Latest Version
2.0.1
Package Id
ember-cli-babel-polyfills@2.0.1
Unpacked Size
368.22 kB
Size
126.36 kB
File Count
7
NPM Version
6.9.0
Node Version
10.16.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
11
25
This addon automatically includes a split build of the Babel polyfills in your
Ember application! This includes three files that are added programmatically
to your index.html
:
polyfill-shared.js
polyfill-evergreen.js
polyfill-legacy.js
The shared file contains the common code between both polyfills, while the
others contain whatever is unique to them. Importantly, the polyfill-legacy
file (which is usually the largest!) is marked with the nomodule
attribute.
This attribute prevents the file from loading in all modern browsers, so it
only impacts your legacy users. For more details, see the
MDN documentation.
It turns out that browsers almost always have inconsistencies, even when they
aren't updating only once-per-Windows-release! For instance, Microsoft Edge does
not yet implement the DOM iterable API as of 01/24/19 (try checking for
document.forms[Symbol.iterator]
in the developer console).
These polyfills are built dynamically using Babel's presetEnv, so they'll stay up to date even as the browsers themselves are changing. Best of all, you only ship the things you care about to modern browsers!
ember install ember-cli-babel-polyfills
Installing the addon will automatically include the polyfills without any additional configuration. You can opt to configure the addon with the following options:
1interface EmberCliBabelPolyfillsConfig { 2 legacyTargets?: string[]; 3 evergreenTargets?: string[]; 4 includeScriptTags?: boolean; 5}
evergreenTargets
The evergreen browsers you want to support, provided in browserslist format. Defaults to the following:
1const evergreenTargets = [ 2 'last 2 Chrome versions', 3 'last 2 Firefox versions', 4 'last 2 Safari versions', 5 'last 2 Edge versions', 6 'last 2 ChromeAndroid versions', 7 'last 2 iOS versions', 8]
Example Usage:
1// ember-cli-build.js
2
3let app = new EmberApp(defaults, {
4 'ember-cli-babel-polyfills': {
5 evergreenTargets: [
6 'last 1 Chrome versions',
7 'last 1 Firefox versions',
8 'last 1 Safari versions',
9 ],
10 },
11});
legacyTargets
The legacy browsers you want to support, provided in browserslist format. Defaults to your app's targets.
Example Usage:
1// ember-cli-build.js 2 3let app = new EmberApp(defaults, { 4 'ember-cli-babel-polyfills': { 5 legacyTargets: [ 6 "last 1 version", 7 "> 1%", 8 "maintained node versions", 9 "not dead", 10 ], 11 }, 12});
includeScriptTags
Whether or not the addon should inject script tags into your content for body
.
Defaults to true
.
Example Usage:
1// ember-cli-build.js
2
3let app = new EmberApp(defaults, {
4 'ember-cli-babel-polyfills': {
5 includeScriptTags: false,
6 },
7});
This project is licensed under the MIT License.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 3/16 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
96 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-30
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