Support MUI v9

[glebcha]

material-react-table version

3.2.1

react & react-dom versions

19.2.5

Describe the bug and the steps to reproduce it

MUI v9 is out and there is massive migration guide with breaking changes.

Is it planned to support v9 or it is supposed to be "plug-n-play"?

Minimal, Reproducible Example - (Optional, but Recommended)

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

None

Terms

• I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

[Tpleme]

Is anyone working on this? i can try to tackle this in the weekend.

[mayerlench]

Any chance this is being upgraded to v9 in the future?

[glebcha]

Any chance this is being upgraded to v9 in the future?

Response from @KevinVandy in twitter:

my ideal plan is that people stop installing material-react-table and just copy and paste the examples here. I'll eventually update the original MRT projects probably, but it's so far down my priority list. This should fix that, hopefully.

Seems MRT should be dropped from our dependencies list and, instead, used customized tanstack table + MUI.

[DarkSorrow]

Well then i guess one day i will just move away from this lib but my lazyness with the help of some LLM helped me update for my project so if people want to check and maybe fork it themselves to manage it feel free :D
https://github.com/novastera/material-react-table
https://www.npmjs.com/package/@novastera-oss/material-react-table

[ohshazbot]

Response from @KevinVandy in twitter:

my ideal plan is that people stop installing material-react-table and just copy and paste the examples here. I'll eventually update the original MRT projects probably, but it's so far down my priority list. This should fix that, hopefully.

What is the context for "examples here"?

[glebcha]

What is the context for "examples here"?

https://tanstack.com/table/alpha/docs/framework/react/examples/lib-material-ui

[glebcha]

Well then i guess one day i will just move away from this lib but my lazyness with the help of some LLM helped me update for my project so if people want to check and maybe fork it themselves to manage it feel free :D https://github.com/novastera/material-react-table https://www.npmjs.com/package/@novastera-oss/material-react-table

In README of your fork there is:

Once MUI v9 reaches a more stable release and correctly fixes the Menu slot types, these components can be reverted to use the standardized slotProps.list pattern if desired for architectural consistency.

But MUI v9 is stable long time ago.
Also lots of "just formatting" changes.
Casting to "any" which seems to be a bad sign, ex. (textFieldProps as any).onBlur?.(event).

Seems that your fork can be a good start point 👍🏻

[DarkSorrow]

Well then i guess one day i will just move away from this lib but my lazyness with the help of some LLM helped me update for my project so if people want to check and maybe fork it themselves to manage it feel free :D https://github.com/novastera/material-react-table https://www.npmjs.com/package/@novastera-oss/material-react-table

In README of your fork there is:

Once MUI v9 reaches a more stable release and correctly fixes the Menu slot types, these components can be reverted to use the standardized slotProps.list pattern if desired for architectural consistency.

But MUI v9 is stable long time ago. Also lots of "just formatting" changes. Casting to "any" which seems to be a bad sign, ex. (textFieldProps as any).onBlur?.(event).

Seems that your fork can be a good start point 👍🏻

Well its not really completely stable, it is still recent and that error about the slotProps was actually because there was a mismatch on the mui v9 code. But i'm using my code in production atm, its working well for the feature i'm using but didn't test all. The storybook works so if some people want to check they are free to do so :p

[glebcha]

Forked and did clean migration with a plan, changes and nuances covered in MIGRATION.md

Vibecode with human power used, no blind acceptance at all. Planning and checking each phase of migration.

NPM package - https://www.npmjs.com/package/@glebcha/material-react-table

Repository - https://github.com/glebcha/material-react-table/tree/v4

[Monabbir-Ahmmad]

One concrete, reproducible breakage for this issue, since the thread is currently about whether v9 is planned rather than what actually breaks.

Versions: material-react-table@3.2.1, @mui/material@9.2.0, React 19.

What breaks

MUI v9 removed MenuListProps from Menu — the list slot is addressed through slotProps.list now. MRT still passes MenuListProps, so it falls through Menu → Popover → Modal and lands on a DOM div:

React does not recognize the `MenuListProps` prop on a DOM element. If you intentionally
want it to appear in the DOM as a custom attribute, spell it as lowercase `menulistprops`
instead. If you accidentally passed it from a parent component, remove it from the DOM
element.

It reproduces on any table with a menu — opening the row-actions menu is enough.

Two effects, and the second is easy to miss:

1. The console error above, on every menu open.
2. The MenuListProps object is silently dropped, so the menu list loses dense (density is no longer applied to menu items) and loses its backgroundColor — the value MRT computes as menuBackgroundColor.

Where

Five call sites, all the same shape:

• src/components/menus/MRT_RowActionMenu.tsx
• src/components/menus/MRT_CellActionMenu.tsx
• src/components/menus/MRT_ColumnActionMenu.tsx
• src/components/menus/MRT_FilterOptionMenu.tsx
• src/components/menus/MRT_ShowHideColumnsMenu.tsx

Fix

The same object moves down one level:

-<Menu
-  MenuListProps={{
-    dense: density === 'compact',
-    sx: { backgroundColor: menuBackgroundColor },
-  }}
+<Menu
+  slotProps={{
+    list: {
+      dense: density === 'compact',
+      sx: { backgroundColor: menuBackgroundColor },
+    },
+  }}
   ...
 />

Compatibility caveat

I have only verified this against 9.2.0. The current peer range is @mui/material: ">=6", so whoever picks this up should confirm slotProps.list is honoured on the oldest supported v6 minor before swapping it unconditionally — I haven't checked that end.

Happy to open a PR if it would be useful — understood from the thread that MRT is low priority right now, so no expectations either way.

[glebcha]

We did our own DataGrid on top of tanstack table and optional MUI.
So, for me now MRT is a kind of legacy that can be dropped.

All who still need MRT as solution, use npm package or fork https://github.com/glebcha/material-react-table/tree/v4 and do whatever you need.

For me the future of MRT seems to be archived as @KevinVandy already mentioned.

The best he can do is to allow community support MRT.