TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error on the columns prop of DataGrid that points at a column's type propertyShort answer
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept. Annotate the array as GridColDef[] so each type value is checked as a literal. Type renderCell params with GridRenderCellParams when the cell callback errors.
Fix it fast
1Find out which cause you have
Find where the columns array is declared. If it has no type annotation and sits outside the component, the next cause applies.
grep -rn "columns\b" src/ | grep -v GridColDef2Match what you see, then jump to its fix
What does the error look like?
A TypeScript error on the columns prop of DataGrid that points at a column's type propertyA TypeScript error inside a column's renderCell callback
Cause 1 of 2
The columns array has no GridColDef type, so type is widened to string
1Check
TypeScript infers an object's string properties as string, not as the literal, because the property might be reassigned. That is the same behaviour as the handbook's method example.
const columns = [
{ field: "age", type: "number" },
];2Fix
Annotate the array with GridColDef[] so the literal is checked against the allowed values.
import { DataGrid, GridColDef } from "@mui/x-data-grid";
const columns: GridColDef[] = [
{ field: "age", headerName: "Age", type: "number" },
];3Verify
Run the type check; the error on columns should be gone.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
A render callback has untyped params
1Check
The Data Grid docs type renderCell params with GridRenderCellParams, where the second generic is the value type of the cell.
grep -rn "renderCell" src/2Fix
Type the params. For a date column the docs use any for the row and Date for the value.
import { GridColDef, GridRenderCellParams } from "@mui/x-data-grid";
const columns: GridColDef[] = [
{
field: "createdAt",
type: "date",
renderCell: (params: GridRenderCellParams<any, Date>) =>
params.value?.toLocaleDateString(),
},
];3Verify
Run the type check again.
npx tsc --noEmitConfirmed by mui.com
How do I stop it coming back?
- Annotate every shared columns array as GridColDef[] when you define it.
- Keep the columns array outside the component or memoized; the docs ask for a stable reference between renders.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fixWeb apps
Upgrading to Next.js 16: middleware becomes proxy, and the other things that break
Missing Required default.js for Parallel Route
Next.js 16 renames middleware.ts to proxy.ts and its exported function to proxy.
6 causes, each with a fix