babel-plugin-formatjs-localized-bundle
A babel plugin to inline translations into compiled formatjs code.
Table of Contents
Getting Started
Installation
npm install @faire/babel-plugin-formatjs-localized-bundle
Usage
Note: your babel configuration will need to be in a Javascript configuration file
To configure the plugin, add it as a babel plugin like the following:
// Example of how you might load translations for a given locale
// translatedMessages could be an object or a path to an object ex. path.resolve(__dirname, `lang/{process.env.BUILD_LOCALE}.json`)
const translatedMessages = getTranslatedMessagesForLanguage(
process.env.BUILD_LOCALE
);
module.exports = {
plugins: [
"@faire/babel-plugin-formatjs-localized-bundle",
{ translatedMessages }, // Options
],
};Options
translatedMessages (Required)
An object or string path to an object of key value pairs where the key represents a string ID and the value represents the translated message.
It is recommended to provide a path to a string that can be loaded by the plugin because it is more performant.
Translated messages can be either strings or compiled formatjs AST.
The values of this object should all be a single language.
Ex.
{
"welcome.message": "Hello",
"button.cta": "Click me"
}additionalFunctionNames (Optional)
Similar to @formatjs/ts-transformer, this allows you to specify additional function names to check besides formatMessage.
additionalComponentNames (Optional)
Similar to @formatjs/ts-transformer, this allows you to specify additional component names to check besides FormatMessage.
onUndefinedMessage (Optional)
Callback function for when an string ID is encountered without a corresponding entry in the translatedMessages object. In this scenario the plugin falls back to the source language.
Building multiple languages
This plugin is intended to inline the translations of a single language into the bundle at a time.
If you are building a project that supports many languages, you can run multiple builds of your application with differing locale configurations (ex. differing environment variables).
An advantage of doing this in multiple builds is the ability to parallelize this work.
Contributing
Issues and PRs are welcome!
This project uses semantic-release to automate version management and package publishing, so make sure to follow the commit message conventions when contributing.