Missing support for Norwegian locales in Chrome >=92 breaks formatjs

[aglunndexcom]

Which package?

This is causing issues in @formatjs/intl-numberformat and @formatjs/intl-datetimeformat, but impacts anywhere that relies on the browser for Intl supported locales.
Polyfilling with @formatjs/intl-pluralrules/should-polyfill can be used to workaround the issue, but only if that polyfill is forced in Chrome with@formatjs/intl-numberformat/polyfill-force.

Describe the bug

Norwegian locales are not currently supported in Google Chrome versions 92 and above, which causes formatjs to fail. The polyfills successfully work around the issue but aren't applied without the (private) polyfill force package because Chrome >= 92 is expected to support these rules.

Here's where the check fails in formatjs:

formatjs/packages/intl/src/create-intl.ts

Line 76 in eb9f193

} else if (!Intl.NumberFormat.supportedLocalesOf(locale).length && onError) {

To Reproduce

Codesandbox URL

Reproducible directly in the browser console window.

Reproducible Steps/Repo

Steps to reproduce the behavior:

1. Open the console window in dev tools of Chrome >=92
2. Check for support for Norwegian locales for Intl NumberFormat by running:
   window.Intl.NumberFormat.supportedLocalesOf(['nb-NO', 'nn-NO', 'en-US'])
   (Similarly, window.Intl.DateTimeFormat.supportedLocalesOf(['nb-NO', 'nn-NO', 'en-US']) will check DateTimeFormat).

Expected behavior

Expectation is an array which includes the Norwegian locales: ["nb-NO", "nn-NO", "en-US"]
Actual: ["en-US"]

Desktop (please complete the following information):

• OS: Any
• Browser: Chrome
• Version: >=92

Additional context

There's an existing Chromium bug reported, but we hope that formatjs may be able to work around the issue for users of this project: https://bugs.chromium.org/p/chromium/issues/detail?id=1215606&q=norwegian&can=2

We are able to patch the issue using polyfill-force but that applies the polyfills to all browsers, would formatjs be able to patch this in a more targeted way?

[longlho]

looks like the fix is to change shouldPolyfill to take in a locale is that right?

[eirslett]

This helped us:

// polyfills.js
// Chrome 92
// https://bugs.chromium.org/p/chromium/issues/detail?id=1215606&q=norwegian&can=2
// https://github.com/formatjs/formatjs/issues/3066
import '@formatjs/intl-datetimeformat/polyfill-force';
import '@formatjs/intl-datetimeformat/locale-data/en';
import '@formatjs/intl-datetimeformat/locale-data/nb';
import '@formatjs/intl-datetimeformat/locale-data/sv';

import '@formatjs/intl-numberformat/polyfill-force';
import '@formatjs/intl-numberformat/locale-data/en';
import '@formatjs/intl-numberformat/locale-data/nb';
import '@formatjs/intl-numberformat/locale-data/sv';

Seems like once you force the locale polyfill, you have to explicitly polyfill every other language too?

[longlho]

You can load those dynamically like

if (shouldPolyfill('nb')) {
	import('@formatjs/intl-numberformat/locale-data/nb');
}