Package Exports
- messageformat-loader
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (messageformat-loader) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
messageformat.js loader for webpack
Dependencies
- Requires messageformat.js 1.0.0 or higher
Install
npm install messageformat-loader
Usage
Documentation: messageformat.js
messages.json
{
"simple-example": "A simple message.",
"var-example": "Message with {X}.",
"plural-example": "You have {N, plural, =0{no messages} one{1 message} other{# messages}}.",
"select-example": "{GENDER, select, male{He has} female{She has} other{They have}} sent you a message.",
"ordinal-example": "The {N, selectordinal, one{1st} two{2nd} few{3rd} other{#th}} message."
}
example.js
var messages = require('messageformat-loader?locale=en!./messages.json');
messages['ordinal-example']({ N: 1 });
// => 'The 1st message.'
Options
locale
The CLDR language code to pass to messageformat.js. Defaults toen
.disablePluralKeyChecks
By default, messageformat.js throws an error when a statement uses a non-numerical key that will never be matched as a pluralization category for the current locale. Use this argument to disable the validation and allow unused plural keys. Defaults tofalse
.intlSupport
Enable or disable support for the default formatters, which require the Intl object. Defaults tofalse
.biDiSupport
Enable or disable the addition of Unicode control characters to all input to preserve the integrity of the output when mixing LTR and RTL text. Defaults tofalse
.formatters
Add custom formatter functions to this MessageFormat instance.strictNumberSign
Follow the stricter ICU MessageFormat spec and throw a runtime error if # is used with non-numeric input. Defaults tofalse
.
License
MIT