build: update dependency webpack to v5.105.0 (21.1.x)

[angular-robot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
webpack	5.104.1 → 5.105.0

---

Release Notes

webpack/webpack (webpack)

v5.105.0

Compare Source

Minor Changes

• Allow resolving worker module by export condition name when using new Worker() (by @​hai-x in #​20353)

• Detect conditional imports to avoid compile-time linking errors for non-existent exports. (by @​hai-x in #​20320)

• Added the tsconfig option for the resolver options (replacement for tsconfig-paths-webpack-plugin). Can be false (disabled), true (use the default tsconfig.json file to search for it), a string path to tsconfig.json, or an object with configFile and references options. (by @​alexander-akait in #​20400)

• Support import.defer() for context modules. (by @​ahabhgk in #​20399)

• Added support for array values ​​to the devtool option. (by @​hai-x in #​20191)

• Improve rendering node built-in modules for ECMA module output. (by @​hai-x in #​20255)

• Unknown import.meta properties are now determined at runtime instead of being statically analyzed at compile time. (by @​xiaoxiaojx in #​20312)

Patch Changes

• Fixed ESM default export handling for .mjs files in Module Federation (by @​y-okt in #​20189)

• Optimized import.meta.env handling in destructuring assignments by using cached stringified environment definitions. (by @​xiaoxiaojx in #​20313)

• Respect the stats.errorStack option in stats output. (by @​samarthsinh2660 in #​20258)

• Fixed a bug where declaring a module variable in module scope would conflict with the default moduleArgument. (by @​xiaoxiaojx in #​20265)

• Fix VirtualUrlPlugin to set resourceData.context for proper module resolution. Previously, when context was not set, it would fallback to the virtual scheme path (e.g., virtual:routes), which is not a valid filesystem path, causing subsequent resolve operations to fail. (by @​xiaoxiaojx in #​20390)

• Fixed Worker self-import handling to support various URL patterns (e.g., import.meta.url, new URL(import.meta.url), new URL(import.meta.url, import.meta.url), new URL("./index.js", import.meta.url)). Workers that resolve to the same module are now properly deduplicated, regardless of the URL syntax used. (by @​xiaoxiaojx in #​20381)

• Reuse the same async entrypoint for the same Worker URL within a module to avoid circular dependency warnings when multiple Workers reference the same resource. (by @​xiaoxiaojx in #​20345)

• Fixed a bug where a self-referencing dependency would have an unused export name when imported inside a web worker. (by @​samarthsinh2660 in #​20251)

• Fix missing export generation when concatenated modules in different chunks share the same runtime in module library bundles. (by @​hai-x in #​20346)

• Fixed import.meta.env.xxx behavior: when accessing a non-existent property, it now returns empty object instead of full object at runtime. (by @​xiaoxiaojx in #​20289)

• Improved parsing error reporting by adding a link to the loader documentation. (by @​gaurav10gg in #​20244)

• Fix typescript types. (by @​alexander-akait in #​20305)

• Add declaration for unused harmony import specifier. (by @​hai-x in #​20286)

• Fix compressibility of modules while retaining portability. (by @​dmichon-msft in #​20287)

• Optimize source map generation: only include ignoreList property when it has content, avoiding empty arrays in source maps. (by @​xiaoxiaojx in #​20319)

• Preserve star exports for dependencies in ECMA module output. (by @​hai-x in #​20293)

• Consider asset modulem to be side-effect free. (by @​hai-x in #​20352)

• Avoid generating JavaScript modules for CSS exports that are not used, reducing unnecessary output and bundle size. (by @​xiaoxiaojx in #​20337)

---

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

[angular-robot]

⚠️ 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: pnpm-lock.yaml

Scope: all 16 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated protractor@7.0.0
.                                        |  WARN  deprecated puppeteer@18.2.1
/tmp/renovate/repos/github/angular/angular-cli/packages/angular_devkit/build_angular:
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 5.105.0 (released 17 hours ago) of webpack does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/angular/angular-cli/packages/angular_devkit/build_angular

The latest release of webpack is "5.105.0". Published at 2/3/2026 3:30:18 PM

Other releases are:
  * legacy: 1.15.0 published at 4/13/2017
  * webpack-2: 2.7.0 published at 7/12/2017
  * webpack-3: 3.12.0 published at 5/11/2018
  * next: 5.0.0-rc.6 published at 10/10/2020
  * webpack-4: 4.47.0 published at 9/6/2023

If you need the full list of all 865 published versions run "$ pnpm view webpack versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude
Progress: resolved 167, reused 0, downloaded 0, added 0