@mui/utils
9.5.0 · 9 Oct 2026MIT21.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @mui/utils From 5.1.0 to 5.17.1
83 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 23
- new
- 36
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking5.9.1
- Breaking5.9.0
- Breaking5.4.2
Security
- 5.15.20
Allow passing
NaNasdefaultValuetouseControlled - 5.9.3
Update packages with security issues
- 5.8.4
[Contributing.md] Local install instructions
- 5.7.0
Update minimist to fix security vulnerability
Release by release
5.16.13 – 5.17.13 releases, nothing new or fixed in the notes
- New
Add
latest-v5tag to v5 releases
- New
5.16.2 – 5.16.85 releases, nothing new or fixed in the notes
- Fixed
Fix React spread key warning in test
- Fixed
5.16.0nothing new or fixed in the note
- Security
Allow passing
NaNasdefaultValuetouseControlled
- Security
5.15.14nothing new or fixed in the note
- Fixed
Fix visually hidden styles' margin unit
- Fixed
187 other lines we could not sort, mostly version bumps
- 5.16.13
Use React 18's JSX runtime for v5.x UMD builds
- 5.16.12
Bump react 19 in v5
- 5.16.8
Skip deep clone React element (v5.x)
- 5.16.6
Use the same CI names on master & next
- 5.16.5
[utils] Add dependency to @mui/types
- 5.16.2
[website] Sync /about page @oliviertassinari
- 5.16.1
⚛️ All packages, including Material UI, are now compatible with React 18.3.1
- 5.16.1
Remove react-test-renderer
- 5.16.1
Replace enzyme in describeConformance
- 5.16.1
Expect React defaultProps warning in test
350 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.