fix(deps): update dependency webpack-merge to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
webpack-merge	^4.2.2 -> ^6.0.1

---

Release Notes

survivejs/webpack-merge (webpack-merge)

v6.0.1

Compare Source

• Fix - Restore usage of clone-deep as there was a corner case where structuredClone did not work as expected. #​214

v6.0.0

Compare Source

• Chore - Update internal dependencies. As a result, the package needs at least Node 18 to run.
• Chore - Use structuredClone over clone-deep dependency since it is included to Node 18 or above. #​214

v5.10.0

Compare Source

• Feat - Support object/array-formed condition for mergeWithRules. #​212

v5.9.0

Compare Source

• Feat - Support deep merging when rule is a merge. #​193, #​206

v5.8.0

Compare Source

• Docs - Update env example to be webpack 5 compatible. #​177, #​180
• Feat - Support strings as rules for TypeScript, not just enums. #​179, #​185

v5.7.3

Compare Source

• Fix - Don't merge strings with objects in mergeWithRules. #​172

v5.7.2

Compare Source

• Fix - If there's no match when using merge operation with mergeWithRules, use default merge behavior as a fallback. #​167

v5.7.1

Compare Source

• Fix - Fix a merge failure for mergeWithRules when non-array matches are merged. #​166

v5.7.0

Compare Source

• Feat - Throw a TypeError if trying to use mergeWithRules with invalid configuration types for append/prepend/merge operations.

v5.6.1

Compare Source

• Fix - Drop extraneous logging.

v5.6.0

Compare Source

• Feat - Support merge (CustomizeRule.Merge) for objects at mergeWithRules. This is useful for merging loader options for example. #​163

v5.5.0

Compare Source

• Feat - Allow mergeWithRules to merge based on rules without a match. #​151 #​159

v5.4.1

Compare Source

• Fix - Allow mergeUnique to work with arbitrary order. #​161

v5.4.0

Compare Source

• Fix - Fall back correctly in mergeWithRules for cases that aren't matched. #​157 #​158
• Fix - Don't throw if using mergeWithRules without a rule #​151
• Feat - Throw if undefined is passed to merge as a structure to merge

v5.3.0

Compare Source

• Fix - Expose Configuration type through a generic to TypeScript to support both webpack 4 and 5 #​141 #​154

In case you use webpack 4, please change your typing as instructed in the readme as the default type is loose but non-breaking.

v5.2.0

Compare Source

• Feature - Support advanced merging cases through mergeWithRules #​146 #​149

v5.1.4

Compare Source

• Fix - Expose CustomizeRule for TypeScript users #​147

v5.1.3

Compare Source

• Fix - Allow merging a RegExp to itself #​145

v5.1.2

Compare Source

• Fix - Allow overriding an object field with null #​144

v5.1.1

Compare Source

• Fix - Drop <reference types="webpack-dev-server" /> from index.d.ts #​143

v5.1.0

Compare Source

• Feature - Expose merge as default for backwards-compatibility with TypeScript. Now import merge from "webpack-merge"; works there. In CommonJS, the default alias is exposed through default property due to technical constraints.

v5.0.9

Compare Source

• Fix - Don't crash on merge() and merge([]). Now {} is returned in these corner cases.

v5.0.8

Compare Source

• Fix - Support Node 10 #​138

v5.0.7

Compare Source

• Fix - Drop tslib dependency by setting "importHelpers": false,

v5.0.6

Compare Source

• Fix - Add tslib to dependencies

v5.0.5

Compare Source

• Tech - Optimize build size (UMD isn't needed)

v5.0.4

Compare Source

• Documentation - Use CommonJS imports at the examples. #​137

v5.0.3

Compare Source

• Feature - Support TypeScript out of the box. #​84 #​86 #​95 #​110 #​112
• Deprecation - merge.smart has been dropped as it's tricky to support all the corner cases. Instead, it's better to use the provided utilities to put together a merge that fits your case.
• Deprecation - mergeStrategy has been dropped in favor of using mergeWithCustomize with customizeArray and customizeObject.
• Deprecation - merge.multiple has been dropped as the functionality was too specific and it's better to implement in the user space if needed.
• Breaking - merge has been moved as a regular import (i.e. import { merge } from 'webpack-merge').
• Breaking - Merge customization has been moved behind mergeWithCustomize.
• Breaking - Bump supported Node version to 12
• Feature - customizeArray supports wildcards now. Example: 'entry.*': 'prepend'. #​45 #​99
• Feature - Throw an error in case a Promise is being merged. It's better to wrap configuration within a Promise and merge inside it. #​81
• Fix - Drop lodash in favor of simpler dependencies. #​134
• Fix - Make unique merge from right to left to match behavior elsewhere. #​119
• Fix - Make sure unique doesn't lose non-unique items to merge. #​125

Special thanks to Google and Addy Osmani for supporting the work financially as it allowed me to complete the work required by the new major release.

v5.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.