MUI date pickers cannot resolve date-fns/addDays
Module not found: Error: Can't resolve 'date-fns/addDays'Short answer
MUI ships different date-fns adapters because date-fns changed how functions are exported in v3. If the adapter you import does not match the date-fns version in node_modules, the bundler cannot resolve a date-fns path. Use AdapterDateFns for date-fns 3 or 4 and AdapterDateFnsV2 for date-fns 2, or upgrade date-fns.
Fix it fast
1Find out which cause you have
List the installed date-fns version next to the MUI package. The adapter you import must match that major version.
npm ls date-fns @mui/x-date-pickers2Match what you see, then jump to its fix
- 1
Can't resolve 'date-fns/...' pointing into a date-fns folder while date-fns is installedThe adapter import does not match the installed date-fns major versionFix - 2
The app worked before updating @mui/x-date-pickers, and the code imports AdapterDateFnsV3The project upgraded across MUI X major versions and the adapter names movedFix
- 1
What does the error look like?
Module not found: Error: Can't resolve 'date-fns/addDays'
Cause 1 of 2
The adapter import does not match the installed date-fns major version
1Check
MUI supports date-fns v2, v3 and v4, and says one adapter cannot serve them all because the way functions are exported changed in v3. Compare your import with the version from the first step.
grep -rn "AdapterDateFns" src2Fix
For date-fns 3 or 4, import AdapterDateFns from @mui/x-date-pickers/AdapterDateFns. For date-fns 2, import AdapterDateFnsV2 from @mui/x-date-pickers/AdapterDateFnsV2.
import { AdapterDateFns } from '@mui/x-date-pickers/AdapterDateFns';
import { LocalizationProvider } from '@mui/x-date-pickers/LocalizationProvider';
<LocalizationProvider dateAdapter={AdapterDateFns}>
<DatePicker />
</LocalizationProvider>3Verify
Restart the dev server and build again.
npm run buildConfirmed by mui.com
Cause 2 of 2
The project upgraded across MUI X major versions and the adapter names moved
1Check
The v7 to v8 migration guide says the v7 AdapterDateFnsV3 became AdapterDateFns, and the v7 AdapterDateFns became AdapterDateFnsV2.
grep -rn "AdapterDateFnsV3\|AdapterDateFnsJalali" src2Fix
Rename the imports to the v8 names, or update date-fns to the latest version, as the guide suggests, so that AdapterDateFns is the right one.
// MUI X v8 names
import { AdapterDateFns } from '@mui/x-date-pickers/AdapterDateFns'; // date-fns 3 or 4
import { AdapterDateFnsV2 } from '@mui/x-date-pickers/AdapterDateFnsV2'; // date-fns 23Verify
Build again.
npm run buildConfirmed by mui.com
How do I stop it coming back?
- Check the date-fns major version before choosing the adapter import.
- Pass the locale from date-fns/locale only in the form your date-fns version expects, as the MUI localization page shows.
- Read the MUI X migration guide when you update to a new major version.
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
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix