-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing locale data for: "en-US". Using default locale: "en" as fallback. #204
Comments
I found the cause of the error:
It doesn't support a properly formatted A workaround:
|
You'll need to load
This is incorrect. The locale data files are provide per language, e.g. |
This is a major refactor of React Intl's build and npm package layout. Locale data is now package-relative and can more easily be loaded: ```js import enLocaleData from 'react-intl/locale-data/en'; ``` There is now only one copy of these locale data files in the package and they are UMD modules which export the locale data for a language. Rollup is now being used to build a _single-file_ React Intl module for three different targets: - `ReactIntl` global: Browser build with bundled dependencies - CommonJS (`main`): For Node/Browserify/Webpack with `require()`-d dependencies - ES6 (`jsnext:main`): For consumption via `import` with `import`-d dependencies All of the builds are compiled with Babel and bundled into a single module file. Rollup is used to fold all of the internal `src/` modules into one. The difference between `lib/index.js` and `lib/index.es.js` is the latter has everything compiled expect the `import`/`export` statements for React Intl as a whole package. The `.babelrc` files have been moved to closer to the source code which they apply. This allows for test or example code to leverage experimental ECMAScript syntax without leaking it into the main src. These changes should result is a smaller and faster package as all of React Intl's code is folded into a single module scope, and the Babel helpers are only included once (instead of per module file). As well as fixing support for IE8. Fixes formatjs#203 Fixes formatjs#204 Fixes formatjs#275 Fixes formatjs#277
This is a major refactor of React Intl's build and npm package layout. Locale data is now package-relative and can more easily be loaded: ```js import enLocaleData from 'react-intl/locale-data/en'; ``` There is now only one copy of these locale data files in the package and they are UMD modules which export the locale data for a language. Rollup is now being used to build a _single-file_ React Intl module for three different targets: - `ReactIntl` global: Browser build with bundled dependencies - CommonJS (`main`): For Node/Browserify/Webpack with `require()`-d dependencies - ES6 (`jsnext:main`): For consumption via `import` with `import`-d dependencies All of the builds are compiled with Babel and bundled into a single module file. Rollup is used to fold all of the internal `src/` modules into one. The difference between `lib/index.js` and `lib/index.es.js` is the latter has everything compiled expect the `import`/`export` statements for React Intl as a whole package. The `.babelrc` files have been moved to closer to the source code which they apply. This allows for test or example code to leverage experimental ECMAScript syntax without leaking it into the main src. These changes should result is a smaller and faster package as all of React Intl's code is folded into a single module scope, and the Babel helpers are only included once (instead of per module file). As well as fixing support for IE8. Fixes formatjs#203 Fixes formatjs#204 Fixes formatjs#275 Fixes formatjs#277
This is a major refactor of React Intl's build and npm package layout. Locale data is now package-relative and can more easily be loaded: ```js import enLocaleData from 'react-intl/locale-data/en'; ``` There is now only one copy of these locale data files in the package and they are UMD modules which export the locale data for a language. Rollup is now being used to build a _single-file_ React Intl module for three different targets: - `ReactIntl` global: Browser build with bundled dependencies - CommonJS (`main`): For Node/Browserify/Webpack with `require()`-d dependencies - ES6 (`jsnext:main`): For consumption via `import` with `import`-d dependencies All of the builds are compiled with Babel and bundled into a single module file. Rollup is used to fold all of the internal `src/` modules into one. The difference between `lib/index.js` and `lib/index.es.js` is the latter has everything compiled expect the `import`/`export` statements for React Intl as a whole package. The `.babelrc` files have been moved to closer to the source code which they apply. This allows for test or example code to leverage experimental ECMAScript syntax without leaking it into the main src. These changes should result is a smaller and faster package as all of React Intl's code is folded into a single module scope, and the Babel helpers are only included once (instead of per module file). As well as fixing support for IE8. Fixes formatjs#203 Fixes formatjs#204 Fixes formatjs#275 Fixes formatjs#277
This is a major refactor of React Intl's build and npm package layout. Locale data is now package-relative and can more easily be loaded: ```js import enLocaleData from 'react-intl/locale-data/en'; ``` There is now only one copy of these locale data files in the package and they are UMD modules which export the locale data for a language. Rollup is now being used to build a _single-file_ React Intl module for three different targets: - `ReactIntl` global: Browser build with bundled dependencies - CommonJS (`main`): For Node/Browserify/Webpack with `require()`-d dependencies - ES6 (`jsnext:main`): For consumption via `import` with `import`-d dependencies All of the builds are compiled with Babel and bundled into a single module file. Rollup is used to fold all of the internal `src/` modules into one. The difference between `lib/index.js` and `lib/index.es.js` is the latter has everything compiled expect the `import`/`export` statements for React Intl as a whole package. The `.babelrc` files have been moved to closer to the source code which they apply. This allows for test or example code to leverage experimental ECMAScript syntax without leaking it into the main src. These changes should result is a smaller and faster package as all of React Intl's code is folded into a single module scope, and the Babel helpers are only included once (instead of per module file). As well as fixing support for IE8. Fixes formatjs#203 Fixes formatjs#204 Fixes formatjs#275 Fixes formatjs#277
I just ran into this issue. So just to clarify, in the following snippet
Is that the expected behavior? What would I need to do if I did want to use |
@SachaG The locale needs to be a BCP-47 language tag. Replace |
Hey @ericf, thanks for your answers. I am getting this in Gatsby w/ community i18n plugin. I have added the
This seems to be workign now via:
|
And clarify that it's an "IETF BCP 47 language tag" [1]. `react-intl`'s doc on `IntlProvider` doesn't currently say that this is the kind of thing it wants for the `locale` prop [2]. But it seems likely: - In 2016, a GitHub "collaborator" said, "The locale needs to be a BCP-47 language tag" [3]. - @formatjs's doc on something else, the `IntlMessageFormat` constructor in the `intl-messageformat` package, takes a similarly-named parameter, `locales` that's documented with, "A string with a BCP 47 language tag, or an array of such strings" [4]. And include a migration, to preserve the user's current setting across the rename. [1] https://en.wikipedia.org/wiki/IETF_language_tag [2] https://formatjs.io/docs/react-intl/components#locale-formats-and-messages [3] formatjs/formatjs#204 (comment) [4] https://formatjs.io/docs/intl-messageformat/#intlmessageformat-constructor
And clarify that it's an "IETF BCP 47 language tag" [1]. `react-intl`'s doc on `IntlProvider` doesn't currently say that this is the kind of thing it wants for the `locale` prop [2]. But it seems likely: - In 2016, a GitHub "collaborator" said, "The locale needs to be a BCP-47 language tag" [3]. - @formatjs's doc on something else, the `IntlMessageFormat` constructor in the `intl-messageformat` package, takes a similarly-named parameter, `locales` that's documented with, "A string with a BCP 47 language tag, or an array of such strings" [4]. And include a migration, to preserve the user's current setting across the rename. [1] https://en.wikipedia.org/wiki/IETF_language_tag [2] https://formatjs.io/docs/react-intl/components#locale-formats-and-messages [3] formatjs/formatjs#204 (comment) [4] https://formatjs.io/docs/intl-messageformat/#intlmessageformat-constructor
The text was updated successfully, but these errors were encountered: