Update dependency @symfony/webpack-encore to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@symfony/webpack-encore	^4.5.0 -> ^5.0.0

---

Release Notes

symfony/webpack-encore (@​symfony/webpack-encore)

v5.0.0

Compare Source

This is a new major version that contains several backwards-compatibility breaks.

Features

• #​1344 Add options configuration callback to Encore.enableReactPreset() (@​Kocal)

• #​1345 Add support for integrity hashes when asset names contain a query string (@​Kocal)

BC Breaks

• #​1321 Drop support of Node.js 19 and 21 (@​Kocal)

• #​1307 Drop webpack-cli 4 support, only webpack-cli ^5.1.4 is supported (@​Kocal)

• #​1318 Drop webpack-dev-server 4 support, only webpack-dev-server 5 is supported (@​Kocal)

The dev-server options have changed between versions 4 and 5, see the official migration guide to v5.
For example:

// With webpack-dev-server 4:
Encore.configureDevServerOptions((options) => {
   options.https = {
     ca: "./path/to/server.pem",
     pfx: "./path/to/server.pfx",
     key: "./path/to/server.key",
     cert: "./path/to/server.crt",
     passphrase: "webpack-dev-server",
     requestCert: true,
   };
});

// With webpack-dev-server 5 (now):
Encore.configureDevServerOptions((options) => {
   options.server = {
      type: 'https',
      options: {
         ca: "./path/to/server.pem",
         pfx: "./path/to/server.pfx",
         key: "./path/to/server.key",
         cert: "./path/to/server.crt",
         passphrase: "webpack-dev-server",
         requestCert: true,
      }
   };
});

• #​1336 Make webpack-dev-server dependency optional (@​Kocal)

The webpack-dev-server package is now an optional peer dependency.
It has been removed because some projects may not use it, and it was installing a bunch of unnecessary dependencies.

Removing the webpack-dev-server dependency from Encore reduces the number of dependencies from 626 to 295 (-331!),
it helps to reduce the size of the node_modules directory and the number of possible vulnerabilities.

To use the webpack-dev-server again, you need to install it manually:

npm install webpack-dev-server --save-dev

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10am every weekday,before 4pm every weekday" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @symfony/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/sass-loader
npm ERR!   sass-loader@"^13.3.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional sass-loader@"^16.0.1" from @symfony/[email protected]
npm ERR! node_modules/@symfony/webpack-encore
npm ERR!   @symfony/webpack-encore@"^5.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/sass-loader
npm ERR!   peerOptional sass-loader@"^16.0.1" from @symfony/[email protected]
npm ERR!   node_modules/@symfony/webpack-encore
npm ERR!     @symfony/webpack-encore@"^5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-10-04T21_10_59_225Z-debug-0.log