Sourced fromjson5's releases.

v2.2.2

• Fix: Properties with the name__proto__ are added to objects and arrays.(#199) This also fixes a prototype pollution vulnerability reported byJonathan Gregson! (#295).

v2.2.1

• Fix: Removed dependence on minimist to patchCVE-2021-44906. (#266)

v2.2.0

• New: Accurate and documented TypeScript declarations are now included. There is no need to install@types/json5. (#236,#244)

v2.1.3 [code,diff]

• Fix: An out of memory bug when parsing numbers has been fixed. (#228,#229)

v2.1.2

• Fix: Bumpminimist tov1.2.5. (#222)

v2.1.1

• New:package.json andpackage.json5 include amodule property sobundlers like webpack, rollup and parcel can take advantage of the ES Modulebuild. (#208)
• Fix:stringify outputs\0 as\\x00 when followed by a digit. (#210)
• Fix: Spelling mistakes have been fixed. (#196)

v2.1.0

• New: Theindex.mjs andindex.min.mjs browser builds in thedist directory support ES6 modules. (#187)

v2.0.1

• Fix: The browser builds in thedist directory support ES5. (#182)

v2.0.0

• Major: JSON5 officially supports Node.js v6 and later. Support for Node.jsv4 has been dropped. Since Node.js v6 supports ES5 features, the code has beenrewritten in native ES5, and the dependence on Babel has been eliminated.

• New: Support for Unicode 10 has been added.

• New: The test framework has been migrated from Mocha to Tap.

• New: The browser build atdist/index.js is no longer minified by default. Aminified version is available atdist/index.min.js. (#181)

• Fix: The warning has been made clearer when line and paragraph separators areused in strings.

• Fix:package.json5 has been restored, and it is automatically generated and

... (truncated)

Sourced fromjson5's changelog.

v2.2.2 [code,diff]

• Fix: Properties with the name__proto__ are added to objects and arrays.(#199) This also fixes a prototype pollution vulnerability reported byJonathan Gregson! (#295).

v2.2.1 [code,diff]

• Fix: Removed dependence on minimist to patchCVE-2021-44906. (#266)

v2.2.0 [code,diff]

• New: Accurate and documented TypeScript declarations are now included. Thereis no need to install@types/json5. (#236,#244)

v2.1.3 [code,diff]

• Fix: An out of memory bug when parsing numbers has been fixed. (#228,#229)

v2.1.2 [code,diff]

• Fix: Bumpminimist tov1.2.5. (#222)

v2.1.1 [code,diff]

• New:package.json andpackage.json5 include amodule property sobundlers like webpack, rollup and parcel can take advantage of the ES Modulebuild. (#208)
• Fix:stringify outputs\0 as\\x00 when followed by a digit. (#210)
• Fix: Spelling mistakes have been fixed. (#196)

... (truncated)

• 14f8cb1 2.2.2
• 10cc7ca docs: update CHANGELOG for v2.2.2
• 7774c10 fix: addproto to objects and arrays
• edde30a Readme: slight tweak to intro
• 97286f8 Improve example in readme
• d720b4f Improve readme (e.g. explain JSON5 better!) (#291)
• 910ce25 docs: fix spelling of Aseem
• 2aab4dd test: require tap as t in cli tests
• 6d42686 test: remove mocha syntax from tests
• 4798b9d docs: update installation and usage for modules
• Additional commits viewable incompare view

Sourced fromeslint-loader's releases.

v4.0.2

Bug Fixes

• use fs-extra ^8.1.0 (7febae0)

v4.0.1

Refactor

• new cache implementation (#320) (6bb1fa6)

v4.0.0

Breaking Changes

• drop support for Node < 10.13.0
• minimum supported eslint version is 6

v3.0.4

Bug Fixes

• #316 updating loader-fs-cache min version (#317) (796e3d1)

v3.0.3

Bug Fixes

• check result object (#311) (6bb1fa6)
• support webpack 5 (#312) (c0a9d0c)

v3.0.2

Bug Fixes

• check if contain results (#300) (7d1d1fe)
• ensure output file path (#299) (16e9ccf)

v3.0.1

Bug Fixes

• module build failed error at Linter.parseResults (#294) (360e69c)

v3.0.0

Bugfix

• fix corrupted filenames if cwd == "/"
• cannot use string formatter in outputReport
• no Output Report in File when build fails under webpack 4
• add posibility to use absolute file path in outputReport.filePath
• it should be possible to use absolute file path in outputReport.filePath
• try load official formatter (#285) (997cce5)
• emit warning/error if no config was found/given (#286) (4204560)

... (truncated)

Sourced fromeslint-loader's changelog.

4.0.2 (2020-04-24)

Bug Fixes

• use fs-extra ^8.1.0 (7febae0)

4.0.1 (2020-04-24)

Refactor

• new cache implementation (#320) (6bb1fa6)

4.0.0 (2020-04-03)

Breaking Changes

• drop support for Node < 10.13.0
• minimum supported eslint version is 6

3.0.4 (2020-04-02)

Bug Fixes

• #316 updating loader-fs-cache min version (#317) (796e3d1)

3.0.3 (2019-12-06)

Bug Fixes

• check result object (#311) (6bb1fa6)
• support webpack 5 (#312) (c0a9d0c)

3.0.2 (2019-09-27)

Bug Fixes

• check if contain results (#300) (7d1d1fe)
• ensure output file path (#299) (16e9ccf)

3.0.1 (2019-09-25)

Bug Fixes

• module build failed error at Linter.parseResults (#294) (360e69c)

... (truncated)

• e732cb5 chore(release): 4.0.2
• 7febae0 fix: use fs-extra ^8.1.0
• ba37e29 chore(release): 4.0.1
• acae2be refactor: new cache implementation (#320)
• c086892 chore(release): 4.0.0
• 1a12052 chore: v4.0.0 (#319)
• 6c6a87a chore(release): 3.0.4
• 953d140 test: jest setTimeout
• acecce6 chore: update deps
• d7be477 chore: update deps
• Additional commits viewable incompare view

Sourced fromlaravel-mix's releases.

v6.0.0

This release brings Laravel Mix current with webpack 5. It additionally includes a variety of bug fixes and enhancements.

• Changelog
• Upgrade Guide

v6.0.0-alpha.0

Add webpack 5 support.

v5.0.5

No release notes provided.

v5.0.0

• Add support forsass-loader 8

v4.0.7

• Fixes file path and compile issues on Windows.

v4.0.0

To Upgrade...

npm remove laravel-mixnpm install laravel-mix@4.0.0

After upgrading, if you encounter anyvue-template-compiler issues, this is related to the fact that your installed version numbers ofvue andvue-template-compiler must be identical. Update one or both to fix this issue.

New

• Faster compiles
• Fasternpm installs.
• Upgraded to webpack 4
• Upgraded to vue-loader 15
• Upgraded to Babel 7
• Automatic vendor extraction. If you callmix.extract() with zero arguments, all vendor dependencies (any package fromnode_modules/ that you pull in) will automatically be extracted. Nifty!
• CSS minification (via cssnano) options may be provided 887808f8aea03b5dabc9e7350b66ee01a52e1610
• PostCSS plugins may be passed to mix.sass/less/stylus() on a per-call basis. This means you may provide unique PostCSS plugins for eachmix.sass() call, if desired. 88690a2f770c071dc8160127c42a4f44decf2b56
• Switched JS optimizing/minification from Uglify to Terser. 5fb180e6e430e99b740a4bce330669cdd8fda29c
• Switched from node-sass to Dart Sass. While this comes with a small increased compile-time cost, the benefit is faster and more reliablenpm installs. 320cecbdb77e222e32903219905d0d8f3754c5ff
• Improved Babel config merging strategy. You may now override or tweak any default Babel plugins and presets provided through Mix by creating a.babelrc file in your project root. 83f5052eb32c498a90edace47402d66eaf80f4b7

Bugfixes

• Allnpm audit alerts have been fixed, thanks to the upgrade to webpack 4.

Notes

• If your project heavily uses JavaScript dynamic imports, you may need to hold off until the release of webpack 5 early next year. There are known compile issues related to this that we cannot fix until then. Once webpack 5 is out, Mix will be updated shortly after.If you're unfamiliar with dynamic imports, then this very likely won't affect your project.
• Sass support is now an on-demand dependency. In prior versions of Mix, thenode-sass andsass-loader dependencies were included out of the box, regardless of whether your project required Sass compilation or not. To help improve install times, these two dependencies will now be installed on-demand if, and only if, your project specifies Sass compilation withmix.sass(). The first time you runnpm run dev, the dependencies will be installed and saved to your dev-dependencies list. 5b7a438bcf53bc87ccc08da09b1e816a6088dec8

... (truncated)

Sourced fromlaravel-mix's changelog.

Changelog

6.0.14

• BabelConfig.fetchBabelRc /static BabelConfig.default /static BabelConfig.generate have all been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
• MixDefinitionsPlugin.getDefinitions andstatic MixDefinitionsPlugin.build have been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
• static Chunks._instance /static Chunks.instance() /static Chunks.reset() are now deprecated and will be removed in a future release.
• The static methods onHotReloading are now deprecated. They have been replaced with instance methods.
• The use of the globalsMix,Config, andwebpackConfig are now deprecated and will warn on use in Mix v7.

We are working toward an API for access toMix for extensions that does not assume that it is a global or that it is the same instance in all cases.

In the mean time:

• Uses ofChunks.instance() may be replaced withMix.chunks
• Uses ofConfig may be replaced withMix.config
• Uses ofwebpackConfig may be replaced withMix.webpackConfig
• Uses ofHotReloading.* methodsMix.hot.*

6.0

View upgrade guide.

Added

• Support for webpack 5
• Newnpx mix executable for triggering your build
• Support for Vue 3 applications
• Support for PostCSS 8
• Newmix.vue() andmix.react() commands
• Newmix.alias() command (Learn More)
• Support for changing the webpack manifest output path (Learn More)
• Newmix.before() hook (Learn More)
• Improvedmix.combine() wildcard support
• Improvedmix.extract() priority and tree-shaking logic

Changed

• Fixed "empty CSS file" extraction bug when using dynamic imports
• Fixedmix.ts() TypeScript bug that skipped Babel transformation in certain cases
• Fixed and improved PostCSS plugin autoloading and merging
• Fixed an issue related to hot module reloading when versioning is enabled
• Added TypeScript types for API

Sourced fromlaravel-mix's upgrade guide.

Upgrade to Mix 6

• Review Your Dependencies
• Check Your Node Version
• Update Your NPM Scripts
• Watch Ignores Node_Modules
• API for JavaScript Frameworks
• Vue Configuration
• Legacy Node Polyfills
• Autoprefixer Options
• Unused Library Extraction
• Automatically Ignored Node Modules
• Did We Miss Something?

npm install laravel-mix@latest

Review Your Dependencies

Laravel Mix 6 ships with support for the latest versions of numerous dependencies, including webpack 5, PostCSS 8, VueLoader 16, and more. These are significant releases with their own sets of breaking changes. We've done our best tonormalize these changes, but it's still particularly important that you take the time to fully test your build afterupgrading to Mix 6.

Please review yourpackage.json dependencies list for any third-party tools or plugins that may not yet be compatiblewith webpack 5 or PostCSS 8.

Check Your Node Version

Mix has bumped its minimum Node requirement from version 8 to 12.14.0. Please check which version you have installed (node -v) and ensure that it meets this requirement.

Update Your NPM Scripts

If your build throws an error such asUnknown argument: --hide-modules, thescripts section of yourpackage.jsonfile will need to be updated. The Webpack 5 CLI removed a number of options that your NPM scripts was likelyreferencing.

While you're at it, go ahead and switch over to the new Mix CLI.

Before

"scripts":{"development":"cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js","watch":"npm run development -- --watch","watch-poll":"npm run watch -- --watch-poll","hot":"cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js","production":"cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"}</tr></table>

... (truncated)

• See full diff incompare view

This version was pushed to npm bythecrypticace, a new releaser for laravel-mix since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from theSecurity Alerts page.