I am running into the following error while trying to deploy vercel code into Azure Web…
- User
I am running into the following error while trying to deploy vercel code into Azure Web App. Help me fix it please: npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: my-v0-project@0.1.0 npm error Found: date-fns@4.1.0 npm error node_modules/date-fns npm error date-fns@"4.1.0" from the root project npm error npm error Could not resolve dependency: npm error peer date-fns@"^2.28.0 || ^3.0.0" from react-day-picker@8.10.1 npm error node_modules/react-day-picker npm error react-day-picker@"8.10.1" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /root/.npm/_logs/2025-07-02T16_50_34_121Z-eresolve-report.txt npm error A complete log of this run can be found in: /root/.npm/_logs/2025-07-02T16_50_34_121Z-debug-0.log
- Assistant
Here’s what’s happening:
- You’ve installed date-fns@4.1.0
- react-day-picker@8.10.1 wants a peer of date-fns@^2.28.0 or ^3.0.0
- npm-v7+ (and v8) enforces peer-dependency resolution by default, so it bails out instead of silently ignoring the mismatch.
You have three main ways to fix this:
1) Align your date-fns version (Recommended)
Since react-day-picker v8.x doesn’t yet support date-fns 4.x, downgrade date-fns to a compatible version:
# 1. Remove the bad install npm uninstall date-fns # 2. Install a version react-day-picker accepts npm install date-fns@^3.0.0 # 3. Re-install your other deps npm installThen re-deploy to Azure.
This keeps your dependency tree “correct” and avoids runtime surprises.
2) Upgrade react-day-picker (if a newer version supports date-fns 4.x)
Check if there’s a newer major of react-day-picker that lists date-fns@4 in its peerDependencies. For example:
npm info react-day-picker@latest peerDependencies # (if you see date-fns@^4.x, you can safely upgrade) npm install react-day-picker@latestIf it still wants date-fns@^2||^3, stick with approach #1.
3) Force-install / legacy-peer-deps (not recommended for prod)
You can override npm’s strictness—but you risk runtime errors:
# one-off npm install --legacy-peer-deps # or set it globally for CI/Azure builds npm config set legacy-peer-deps trueThis will ignore the conflict and pull in both date-fns v4 and the unmet peer, but if react-day-picker calls something that changed in v4 you could see bugs.
After your fix
- Commit your updated
package.json&package-lock.json. - Push to your repo / trigger your Azure pipeline.
- Verify in the Azure Web App logs that
npm installnow completes without ERESOLVE errors.
Let me know which approach you try or if you hit any other errors! 🚀
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.