Update webpack 5.90.1 → 5.90.2 (patch)

[depfu[bot]]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ webpack (5.90.1 → 5.90.2) · Repo

Release Notes

5.90.2

Bug Fixes

• use Math.imul in fnv1a32 to avoid loss of precision, directly hash UTF16 values
• the setStatus() of the HMR module should not return an array, which may cause infinite recursion
• __webpack_exports_info__.xxx.canMangle shouldn't always same as default
• mangle export with destructuring
• use new runtime to reconsider skipped connections activeState
• make dynamic import optional in try/catch
• improve auto publicPath detection

Dependencies & Maintenance

• improve CI setup and include Node.js@21

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 30 commits:

• chore(release): 5.90.2
• fix: improve auto publicPath detection
• test: update
• test: update
• fix: improve auto publicPath detection
• ci: update
• ci: update azure
• ci: update
• chore(deps): update
• ci: update
• ci: update
• test: case for issue-17459
• test: use production
• test: case for issue-17459
• fix: make dynamic import optional in try/catch
• fix: make dynamic import optional in try/catch
• fix: use new runtime to reconsider skipped connections activeState
• update snapshot
• add test
• fix: should use new runtime to reconsider skipped connections
• fix: mangle export with destructuring
• add test
• fix: not mangle export with destructuring
• fix: __webpack_exports_info__.xxx.canMangle shouldn't always same as default
• fix: __webpack_exports_info.xxx.canMangle should not always same as default
• fix: The `setStatus()` of the HMR module should not return an array, which may cause infinite recursion
• fix: use Math.imul in fnv1a32 to avoid loss of precision, directly hash UTF16 values
• (chore) Update comment
• Update test cases
• Use Math.imul in fnv1a32, operate directly on UTF-16

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)