finds.dev← search

// the find

KevinVandy/material-react-table

★ 1,800 · TypeScript · MIT · updated Jun 2026

A fully featured Material UI V5 implementation of TanStack React Table V8, written from the ground up in TypeScript

A high-level wrapper around TanStack Table V8 that wires it up to Material UI components, giving you a fully interactive data grid with sorting, filtering, pagination, row selection, editing, virtualization, and drag-and-drop out of the box. It targets React teams already committed to the MUI ecosystem who want a production-ready table without assembling all the pieces themselves. Not a replacement for TanStack Table — it's a batteries-included layer on top of it.

The feature coverage is genuinely impressive for a single-maintainer library: five editing modes, server-side pagination/sorting/filtering, column pinning, row virtualization via @tanstack/react-virtual, and built-in i18n with a dozen locales. The TypeScript generics flow through correctly so column definitions are typed against your data shape, which is the thing that breaks most table libraries. The `useMaterialReactTable` hook pattern separates table configuration from rendering, which makes it straightforward to read table state from outside the component. Documentation has live editable examples for almost every feature, which saves hours of trial and error.

You're taking on the full MUI peer dependency tree — @mui/material, @mui/x-date-pickers, @mui/icons-material, @emotion/react, @emotion/styled — before you even install the package itself. If you're not already on MUI, the bundle cost is a dealbreaker. The abstraction also buries TanStack Table's lower-level API behind MUI-specific prop names (muiTableHeadCellProps, muiTableBodyRowProps, etc.), so when you need to do something the wrapper doesn't anticipate, you're digging through two layers of docs. At 1.8k stars it has a relatively small community compared to AG Grid or react-data-grid, which means fewer Stack Overflow answers and slower issue triage. The Mantine React Table sibling repo suggests the author is maintaining two parallel implementations, which is a maintenance risk worth watching.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →