'useFormatter' hydration error in Azerbaijani

[KamranV21]

Description

When formatting a date using useFormatter with the 'az' locale, I encounter a hydration error. While server-side formatting works as expected, client-side formatting results in an invalid format like 2025 M02 11 20:35:35, which causes a hydration issue.

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://codesandbox.io/p/devbox/wild-worker-5t6rvx?file=%2Fsrc%2Fapp%2F%5Blocale%5D%2Fpage.tsx%3A7%2C34

Reproduction description

Steps to reproduce:

1. Open reproduction
2. Open console
3. Switch to Azerbaijani language
4. Observe invalid date format

Expected behaviour

The date is expected to be formatted correctly on both the client-side and server-side.

[amannn]

Hey, it seems like this is a Chrome-only issue related to the Intl.DateTimeFormat API.

You can verify by running this in Chrome in your console:

// 2025 M02 12 11:13:44
new Intl.DateTimeFormat('az', {dateStyle: "long", timeStyle: "medium",}).format(new Date())

In Safari and Firefox I see the correct behavior. In the latest Node.js version the formatting is also fine.

Maybe you want to file a bug at the Chromium bug tracker?

In regard to your app, maybe you can find a setting that avoids the issue, e.g.:

// "'2025-02-12 11:19:55'"
new Intl.DateTimeFormat('az', {dateStyle: "short", timeStyle: "medium",}).format(new Date())

[KamranV21]

@amannn

Yes, you must be right. This error only appears on Chrome-based browsers. I've created an issue in their bug-tracker. Thank you!

[amannn]

Awesome, thanks! Can you leave your created ticket here for reference?

[KamranV21]

Sure. Here is the link to the related issue on Chromium:
https://issues.chromium.org/issues/396060189