i18n/explicit-locale

Dlaczego

Without a locale, formatting follows the browser or server default. A Polish page then shows English dates to a visitor with an English browser, and server rendering (often en-US in a container) produces text that differs from the client, which causes hydration mismatches.

Poprawka

Pass the locale the app uses for its messages (from the router, the i18n library or <html lang>), and set timeZone explicitly when rendering dates on the server.

Przykłady

// bad
date.toLocaleDateString()
// good
date.toLocaleDateString(locale, { dateStyle: 'long', timeZone })

Źródła

• MDN, Intl (locales argument)
• MDN, Date.prototype.toLocaleDateString()

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain i18n/explicit-locale