Dev Error: date-fns "en" import fails but works in production

Discussions
1

Hi V0 team,

I’m encountering a runtime error only in the development environment of my project on V0:

javascript

Runtime Error: The "date-fns" module does not provide an export named "en".

This does not happen in production, where everything works fine.

After investigating, it seems the issue stems from a change in how the date-fns library handles locale imports. Older versions allowed this:

js

CopiarEditar

import { en } from 'date-fns/locale'; // ❌ (now broken)

But in newer versions, it needs to be:

js

CopiarEditar

import enUS from 'date-fns/locale/en-US'; // ✅

My guess is that the dev environment on V0 is using a newer version of date-fns than production, which leads to this discrepancy.

Could you please:

  • Confirm whether the dev environment is using a different version of date-fns than prod?
  • Either align the versions across environments or allow us to specify/fix dependency versions to avoid unexpected breaks.

Thanks in advance — this is currently blocking development.

Best,

4

You’re killing the product with this credits system.
We’re now being charged to fix your errors.
Iteration is punished. Creativity is taxed.
We’re paying more, getting less.
This is not transparency—it’s exploitation.

RT to raise our voice
#SaveV0