Message file formats

You can use any message syntax and file formats with Paraglide JS via inlang plugins.

By default, Paraglide JS uses the inlang-message-format plugin, but you can use any other plugin that suits your needs. Mixing & matching is also possible.

Available plugins

All plugins can be found on https://inlang.com/c/plugins. Here are some popular plugins:

• Inlang Message Format
• JSON
• i18next

Installing a plugin

Add the link of the plugin to the modules in the settings.json file.

{
  "baseLocale": "en",
  "locales": ["en", "de"],
  "modules": [
     "other plugins...",
+    "https://cdn.jsdelivr.net/npm/@inlang/plugin-message-format@latest/dist/index.js"
  ]
}

Using multiple plugins

You can use multiple plugins in your project.

{
  "baseLocale": "en",
  "locales": ["en", "de"],
  "modules": [
     "other plugins...",
+     "https://cdn.jsdelivr.net/npm/@inlang/plugin-message-format@latest/dist/index.js"
+     "https://cdn.jsdelivr.net/npm/@inlang/plugin-i18next@latest/dist/index.js"
  ]
}

Implementation Details

We learned the hard way that a binary .inlang file is needed to make localization simple. Unfortunately, git can't store binary files without losing the benefits of version control.

Hence, for now, unpacking .inlang files into directories and creating an in-memory sqlite on each load is the way to go.

Good-to-know: .inlang files

The long-term vision is to use .inlang files directly without depending on external message files and plugins.