Bump serialize-javascript and laravel-mix in /web/themes/custom/pece_theme

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Removes serialize-javascript. It's no longer used after updating ancestor dependency laravel-mix. These dependencies need to be updated together.

Removes serialize-javascript

Updates laravel-mix from 5.0.5 to 6.0.49

Release notes

Sourced from laravel-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.

Changelog

Sourced from laravel-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 and static 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 on HotReloading are now deprecated. They have been replaced with instance methods.
• The use of the globals Mix, Config, and webpackConfig are now deprecated and will warn on use in Mix v7.

We are working toward an API for access to Mix 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 of Chunks.instance() may be replaced with Mix.chunks
• Uses of Config may be replaced with Mix.config
• Uses of webpackConfig may be replaced with Mix.webpackConfig
• Uses of HotReloading.* methods Mix.hot.*

6.0

View upgrade guide.

Added

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

Changed

• Fixed "empty CSS file" extraction bug when using dynamic imports
• Fixed mix.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

Upgrade guide

Sourced from laravel-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, Vue Loader 16, and more. These are significant releases with their own sets of breaking changes. We've done our best to normalize these changes, but it's still particularly important that you take the time to fully test your build after upgrading to Mix 6.

Please review your package.json dependencies list for any third-party tools or plugins that may not yet be compatible with 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 as Unknown argument: --hide-modules, the scripts section of your package.json file will need to be updated. The Webpack 5 CLI removed a number of options that your NPM scripts was likely referencing.

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)

Commits

• See full diff in compare view

Maintainer changes

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