product icon

JSON translation files


#What does this plugin do?

This plugin is a general purpose plugin to read and write messages of json files.

#Manual Installation

We recommend using the install button, but if you want to do it manually:

  • Add this to the modules in your project.inlang/settings.json
  • Change the sourceLanguageTag if needed
  • Include existing languagetags in the languageTags array
	"sourceLanguageTag": "en",
	"languageTags": ["en", "de"],
	"modules": [""],
	"plugin.inlang.json": {
		"pathPattern": "./resources/{languageTag}.json"



	"hello": "Hello {name}!",
	"loginButton": "Login"


	"hello": "Hallo {name}!",
	"loginButton": "Anmelden"


The plugin offers further configuration options that can be passed as arguments. The following settings exist:

Here is the syntax for the PluginSettings object in TypeScript:

type PluginSettings = {
	pathPattern: string | { [key: string]: string }
	variableReferencePattern?: [string] | [string, string]
	ignore?: string[]


To use our plugin, you need to provide a path to the directory where your language-specific files are stored. Use the dynamic path syntax {languageTag} to specify the language name.

#Without namespaces

"plugin.inlang.json": {
	"pathPattern": "./resources/{languageTag}.json"

#With namespaces

Does not get created by 'npx @inlang/cli config init'

"plugin.inlang.json": {
	"pathPattern": {
		"website": "./resources/{languageTag}/website.json",
		"app": "./resources/{languageTag}/app.json"


Defines the pattern for variable references. The default is how i18next suggests the usage of placeholders.


"plugin.inlang.json": {
	"variableReferencePattern": ["{", "}"]

Common use cases

{placeholder}["{", "}"]
{{placeholder}}["{{", "}}"]
${placeholder}["${", "}"]
[placeholder]["[", "]"]


An array of strings that are used to ignore certain files. The strings are matched against the file path. If the file path contains the string, the file is ignored.

"plugin.inlang.json": {
	"ignore": ["node_modules", "dist"]

#Expected behavior

The message IDs are sorted in the order in which they appear in the sourceLanguage file. The nesting or flattening of IDs is detected on a file-by-file basis. If the sourceLanguage file contains nested IDs, the plugin will also create nested IDs in the targetLanguage files. If the sourceLanguage file contains flattened IDs, the plugin will also create flattened IDs in the targetLanguage files.

#Supercharge your i18n workflow by installing the Inlang Visual Studio Code extension (Sherlock)

The plugin can be used with Sherlock - VS Code extension to extract keys from your code, display inline annotations, have quality checks with lint rules & more. There are only 2 steps to get started:

  1. Install: VS Code Marketplace.
  2. Add the correct syntax matcher:
  3. Optional: Add lint rules:
  4. 🎉 Done!


#Getting started

Run the following commands in your terminal (node and npm must be installed):

  1. npm install
  2. npm run dev

npm run dev will start the development environment which automatically compiles the src/index.ts files to JavaScript (dist/index.js), runs tests defined in *.test.ts files and watches changes.


Run npm run build to generate a build.

The dist directory is used to distribute the plugin directly via CDN like jsDelivr. Using a CDN works because the inlang config uses dynamic imports to import plugins.

Read the jsDelivr documentation on importing from GitHub.

Is something unclear or do you have questions? Reach out to us in our Discord channel or open a Discussion or an Issue on Github.