The renderInput prop stopped working on the MUI X DatePicker
renderInput does nothing on DatePicker, or TypeScript says the prop does not existShort answer
renderInput was removed from the MUI X date pickers in version 6. Put the text field settings in slotProps.textField instead. Two other v5 patterns break in the same upgrade: the locale prop on LocalizationProvider is now adapterLocale, and date adapters come from @mui/x-date-pickers, not @date-io.
Fix it fast
1Find out which cause you have
Check which version of the pickers package is installed. renderInput belonged to version 5; from version 6 it is gone.
npm ls @mui/x-date-pickers2Match what you see, then jump to its fix
- 1
The text field looks like the default one and ignores your TextField propsrenderInput was removed in v6Fix - 2
The picker ignores the language you set, for example locale="fr"The locale prop on LocalizationProvider was renamedFix - 3
Import errors from @date-io packages after the upgradeDate adapters are imported from the old @date-io packagesFix
- 1
What does the error look like?
renderInput does nothing on DatePicker, or TypeScript says the prop does not existThe custom TextField (variant, size, helperText) is ignoredAdapters imported from @date-io no longer work after upgrading the pickers
Cause 1 of 3
renderInput was removed in v6
1Check
Search for renderInput in the code. In v6 and later the prop is gone and the picker renders its own text field.
grep -rn "renderInput" src/2Fix
Move the TextField props into slotProps.textField.
// before (v5)
<DatePicker renderInput={(params) => <TextField {...params} variant="outlined" />} />
// after (v6 and newer)
<DatePicker slotProps={{ textField: { variant: 'outlined' } }} />3Verify
The picker renders with the variant you set.
grep -rn "renderInput" src/Confirmed by raw.githubusercontent.com
Cause 2 of 3
The locale prop on LocalizationProvider was renamed
1Check
Look at how LocalizationProvider receives the locale.
grep -rn "LocalizationProvider" src/2Fix
Rename the prop to adapterLocale.
<LocalizationProvider dateAdapter={AdapterDayjs} adapterLocale="fr">
{children}
</LocalizationProvider>3Verify
Open the picker. Month and weekday names are in the chosen language.
# open the picker in the browserConfirmed by raw.githubusercontent.com
Cause 3 of 3
Date adapters are imported from the old @date-io packages
1Check
From v6 the adapters cannot be imported from @date-io. Look for those imports.
grep -rn "@date-io" src/ package.json2Fix
Import the adapter from @mui/x-date-pickers. For Luxon, version 3.0.2 or newer is needed.
// example: the Jalaali adapter
import { AdapterMomentJalaali } from '@mui/x-date-pickers/AdapterMomentJalaali';3Verify
The app builds and the picker opens.
npm run buildConfirmed by raw.githubusercontent.com
How do I stop it coming back?
- Read the migration guide before raising a major version of the pickers package.
- Search the code for renderInput, locale= and @date-io right after a major upgrade.
- Pin the pickers package to a major version in package.json.
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
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
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.
2 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