🦄 The whole family is now on Mantine 9.6.0

Mantine 9.6.0 came out this morning, and by the afternoon the whole Mantine Extensions family was on it — all 26 components plus the Nextra and Fumadocs starter templates.

The reason I chase these on release day isn't tidiness. It's that the gap between "upstream shipped" and "the extension you depend on tracks it" is where trust in a small library actually lives. Peer ranges here stay at >=9.0.0, so none of this forces anything on you — bump when you want.

What's actually new in 9.6, in case you missed it

  • A whole new package, /lightbox — full-screen media lightbox with carousel, zoom, thumbnails and video slides. Mount it once and open it from anywhere, same store pattern as Spotlight.

  • ActionBar in core — the fixed bottom bar for bulk actions on a selection. If you've ever hand-rolled one of these (portal, z-index, transition, Escape), this is the part you can now delete.

  • Four new charts: GaugeChart, WaffleChart, MatrixChart, CandlestickChart, plus referenceAreas and referenceDots on the cartesian ones.

  • Notifications got renderNotification — you replace the entire notification and keep the enter/exit/drag-dismiss animations, which is usually the thing that stops people customising them.

One tip that cost me a wrong "done" today. If you're on Next 16.3+, Turbopack's FileSystem Cache is on by default for builds and it does not invalidate on node_modules. So a next build right after a dependency bump can replay a cache compiled against the old version and hand you a green build that proves nothing. Delete .next after changing deps, or your verification is theatre. I'd written that trap down months ago and still walked into it — my build script only cleaned dist.

The upgrade also surfaced two gaps in my own components, both filed as issues instead of rushed out: core's FloatingWindow now has a complete six-callback drag/resize lifecycle where my Window exposes two, and that new ActionBar is the missing other half of the row selection ListViewTable already supports.

If you're using any of these in something real, I'd genuinely like to know which ones — the roadmap follows what people actually reach for, and the two issues above came straight from reading upstream against my own API.

npm:

Docs:

GitHub:

8 views

Add a comment

Replies

Be the first to comment