Update dependency webpack-bundle-analyzer to v5.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
webpack-bundle-analyzer	5.3.1 → 5.4.0

---

Release Notes

webpack/webpack-bundle-analyzer (webpack-bundle-analyzer)

v5.4.0

Compare Source

Minor Changes

• Use Webpack's infrastructure logger when available (compiler.getInfrastructureLogger('webpack-bundle-analyzer')) and deprecate the plugin's logLevel option in favor of Webpack's native infrastructureLogging configuration. (by @​ronakmaheshwari in #​738)

v5.3.3

Compare Source

Patch Changes

• Scope parsed module sources to the asset they were parsed from, so assets that reuse the same module IDs, or that share a module, no longer report each other's parsed and compressed sizes. (by @​Menny1337 in #​734)

v5.3.2

Compare Source

Patch Changes

• Parse Webpack 5 module maps nested in UMD wrappers, using bundle module IDs and Webpack runtime structure to choose among IIFE candidates. (by @​Menny1337 in #​733)

• Improve report generation performance for compilations with many assets. (by @​christiango in #​723)

• Resolve bundle assets and report files against the correct compiler output path when a plugin instance is shared by multiple compilers. (by @​utkarshalpha in #​725)

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • "after 2am and before 8am on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eesast-web@2024.0.0
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   graphql@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^15.0.0 || ^16.0.0" from @apollo/client@3.14.1
npm error node_modules/@apollo/client
npm error   @apollo/client@"3.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-05T18_45_33_049Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-05T18_45_33_049Z-debug-0.log

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request