Bump webpack from 5.98.0 to 5.105.0 in /preview

[dependabot]

Bumps webpack from 5.98.0 to 5.105.0.

Release notes

Sourced from webpack's releases.

v5.105.0

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)

... (truncated)

Changelog

Sourced from webpack's changelog.

5.105.0

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)

... (truncated)

Commits

• 1486f9a chore(release): new release
• 1a517f6 feat: added the tsconfig option for the resolver options (#20400)
• 7b3b0f7 feat: support import.defer() for context modules
• c4a6a92 refactor: more types and increase types coverage
• 5ecc58d feat: consider asset module as side-effect-free (#20352)
• cce0f69 test: avoid comma operator in BinaryMiddleware test (#20398)
• cd4793d feat: support import specifier guard (#20320)
• fe48655 docs: update examples (#20397)
• de107f8 fix(VirtualUrlPlugin): set resourceData.context to avoid invalid fallback (#2...
• a656ab1 test: add self-import test case for dynamic import (#20389)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for webpack since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

This change is 

[fadi-george]

@claude review

[claude]

Claude finished @fadi-george's task in 1m 51s —— View job

---

Review of Webpack 5.98.0 → 5.105.0 Update

Summary

This Dependabot PR updates webpack from 5.98.0 to 5.105.0 in the /preview directory. After analyzing the codebase and changes, I have the following findings:

Key Findings

1. Limited Impact Scope

• Webpack is only a devDependency in /preview/package.json
• The main project uses Vite for building (not webpack) - see root package.json:74
• No webpack configuration files found in the preview directory
• No webpack build scripts defined in preview/package.json:6-9
• Webpack appears to be unused or minimally used in this directory

2. Update Analysis

The update includes 7 minor features and 16 patch fixes. Notable changes:

Minor Changes:

• New tsconfig resolver option (replacement for tsconfig-paths-webpack-plugin)
• Support for import.defer() in context modules
• Array values support for devtool option
• Improved ESM module rendering for Node built-ins
• Runtime determination of unknown import.meta properties
• Conditional import detection to avoid compile-time linking errors

Patch Changes:

• Multiple ESM and Module Federation fixes
• Worker module handling improvements
• import.meta.env behavior fixes
• TypeScript type improvements
• Source map generation optimizations

3. Risk Assessment

✅ Low Risk - This update appears safe because:

• No breaking changes identified in the changelog
• Webpack is not actively used in the build pipeline (main project uses Vite)
• All changes are backward-compatible minor/patch updates
• The update includes multiple bug fixes and optimizations

4. Testing Recommendations

Even though webpack appears unused, I recommend:

1. Verify the preview server still functions: npm start in the preview directory
2. Check if any docker-compose builds rely on webpack (see preview/README.md)
3. Run any existing test suites that might use the preview environment

Recommendation

✅ Approve with minimal risk

This dependency update is safe to merge. The changes are entirely in the /preview directory where webpack is listed as a devDependency but doesn't appear to have any active usage. If webpack is truly unused, consider removing it from the dependencies in a future cleanup PR to reduce the dependency footprint.

---

Related Questions:

• Is webpack intentionally kept for future use, or can it be removed from preview/package.json?
• Are there any undocumented build processes that might use webpack?

---

• Read repository guidelines (CLAUDE.md)
• Examine package-lock.json changes
• Check for webpack configuration files
• Review webpack changelog for breaking changes
• Analyze security and compatibility implications
• Provide comprehensive review feedback

---