Installations

npm install laravel-mix-polyfill

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

12.22.1

NPM Version

6.14.12 Score

42.5

Supply Chain

48

Quality

66.2

Maintenance

50

Vulnerability

94.6

License

Pull Requests

Open

0

Total

4

Closed

0

Merged

4

Issues

Open

6

Total

34

Closed

28

Releases

4

v3.0.1

Updated on May 27, 2021

v3.0.0

Updated on Jan 05, 2021

v2.0.0

Updated on Feb 10, 2020

v1.1.1

Updated on Feb 10, 2020

View All 4 releases

Languages

1

JavaScript

JavaScript (100%)

Developer

scottcharlesworth

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

MIT License

48 Stars

57 Commits

6 Forks

3 Watchers

1 Branches

1 Contributors

Updated on Apr 26, 2025

Maintainers

1

View All 1 Contributors

Package Meta Information

Latest Version

3.0.1

Package Id

laravel-mix-polyfill@3.0.1

Unpacked Size

8.69 kB

Size

3.54 kB

File Count

8

NPM Version

6.14.12

Node Version

12.22.1

Total Downloads

Cumulative downloads

Total Downloads

NaN

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

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

2

core-js regenerator-runtime

Peer Dependencies

1

laravel-mix

Laravel Mix Polyfill

A Laravel Mix extension to include polyfills by using Babel, core-js, and regenerator-runtime.

Usage

First, install the extension.

npm install laravel-mix-polyfill --save-dev

or

yarn add laravel-mix-polyfill --dev

Then, require it within your webpack.mix.js file:

1let mix = require('laravel-mix');
2
3require('laravel-mix-polyfill');
4
5mix.js('resources/js/app.js', 'public/js')
6   .sass('resources/sass/app.scss', 'public/css')
7   .polyfill({
8      enabled: true,
9      useBuiltIns: "usage",
10      targets: "firefox 50, IE 11"
11   });

Options

Name	Type	Default	Description
enabled	`boolean`	`true`	Should polyfill be used.
useBuiltIns	`string`	`"usage"`	See here for detailed description. Possible values are: • `"usage"` • `"entry"` • `false`
targets	`string`, `boolean`	`"defaults"`	Allows a target (browser) environment to be specified. This can either be: • a browserslist-compatible query (`"> 0.25%, not dead"`), • or `false` to transform all ECMAScript 2015+ code by default. • Setting to `false` will also allow use of browserslist config sources (like .browserslistrc). See here and here for more information. You can test string values on browserl.ist.
entryPoints	`string`, `boolean`	`"stable"`	Used when `useBuiltIns` is set to `"entry"`. See below for possible values.
corejs	`number`	`3`	The version of core-js to be used.
debug	`boolean`	`false`	Outputs the targets/plugins used to the console.

Entry Points

In core-js@3 the entry points were changed to allow for more flexibility.

The following common presets have been included for ease, and will be inserted into the entry point for you automatically. "stable" has been set as the default as it is a full equal of the now deprecated @babel/polyfill package which was used previously.

Value	Description
`"stable"`	Polyfill only stable `core-js` features - ES and web standards.
`"all"`	Polyfill all `core-js` features.
`"es"`	Polyfill only stable ES features.
`"classic"`	Imports copied from the latest `@babel/polyfill` package (before it was deprecated).
`false`	Do not use a preset (you will need to add your own imports to the top of your entry point).

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Maintained

Determines if the project is "actively maintained".

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

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