Plural translations (with count paramater) produce "does not match server-rendered HTML" ("ua" locale)

[nikitastryuk]

Description

Plural translations (with count paramater) which uses "Intl.PluralRules" API determined incorrectly on server ("ua" locale).

Issue
{ "test": "{count, plural, one {# user} other {# users}}" }

<p>{t('test', { count: 21 })}</p>

#other is returned from server-rendered html and then transformed to #one on client side.

Mandatory reproduction URL (CodeSandbox or GitHub repository)

Codesandbox

Reproduction description

To Reproduce

1. Go to Codesandbox
2. Insert /ua to url
3. Press Enter
4. See Hydration error
5. Press enter more times (with url focused) to see blinking translations

Expected behaviour

Plural translations should behave the same on both server and client.

[nikitastryuk]

UPD after some debugging and investigation:

It started working with uk instead of ua. Looks like Intl.PluralRules works with codes from this list only.

But still not sure why server side initial result is different.

[amannn]

Node.js and browsers seem to have subtle differences when it comes to the implementation of Intl. We saw a similar issue here: #528

[amannn]

This seems to be out of control for next-intl and is related to the underlying runtime. You might have to provide polyfills for a consistent environment.