chore(deps): update dependency webpack to v4.46.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
webpack	4.41.2 -> 4.46.0

---

Release Notes

webpack/webpack

v4.46.0

Compare Source

Bugfixes

• fix behavior of defaults for resolve.roots to be backward-compatible

v4.45.0

Compare Source

Features

• resolve server-relative requests relative to project context by default

Bugfixes

• fix a bug where splitChunk minSize is not handled correctly
• fix a bug where the order of splitChunk cacheGroups is not handled correctly

v4.44.2

Compare Source

Bugfixes

• make sure to generate correct chunk connection for blocks that are only connected in some runtimes
  • fixes a bug where filename contains undefined hash at runtime

v4.44.1

Compare Source

Bugfixes

• fix bug in sideEffects optimization when using export * from "non-esm" and a default export.
• add missing optional peerDependencies for webpack-cli and webpack-command to support Yarn 2

v4.44.0

Compare Source

Features

• Improve sideEffects flag behavior when dynamic modules are part of the tree
  • Fixes a bug which causes empty modules (or type-only modules) to "break" Tree Shaking
• add splitChunks.enforceSizeThreshold to allow enfore splitting larger chunks unrelated from other limiations
  • Not set by default to avoid breaking change
  • It will be set by default to 50k in webpack 5
  • It's recommended to set it in webpack 4 too
• add support for resolve.roots and default resolve.roots: [context]
  • This allows to resolve server-relative urls (e.g. /src/abc) to the project root (or other locations when configured)
  • This allows to use loaders that rely on that behavior

Bugfixes

• fix bug where splitChunks produced non-optimal results when minSize is set to 0
  • This lead to NaNs in some places which breaks ordering
• Fix bug which lead to HMR not working for splitChunks in entrypoints
• force update watchpack and chokidar for chokidar bugfix which causes files to stop being watched

v4.43.0

Compare Source

Features

• add module.hot.invalidate() to HMR API

Dependencies

• push versions for forced security updates

v4.42.1

Compare Source

Bugfixes

• update webassemblyjs dependencies for instruction update
• update mkdirp dependency for security reasons

v4.42.0

Compare Source

Bugfixes

• Disable constant replacements in "use asm" scope
• Update schema to disallow functions for output.hotUpdateChunkFilename as this doesn't work
• Hoist exports in concatenated module to handle circular references with non-concatenated modules correctly
• Flag all modules as used in DLLs to fix missing exports

v4.41.6

Compare Source

Bugfixes

• Windows network paths are considered as absolute paths
• fix hanging of FlagDependencyExportsPlugin when using export * in a circular matter

v4.41.5

Compare Source

Bugfixes

• handle relative paths with webpack:// prefix in SourceMaps correctly
• fixes a non-determinism about providedExports with export * which caused changing module hashes and unnecessary HMR invalidation

v4.41.4

Compare Source

Bugfixes

• fix case where __webpack_require__.e is not a function when using module concatenation
• fix incorrect imported module when using sideEffects in a certain constellation of export names

Performance

• lazy-require Webassembly related modules for improved startup performance

v4.41.3

Compare Source

Security

• force upgrade terser-webpack-plugin dependency for security fix (not affecting webpack)

Funding

• add npm funding field to package.json

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.