> For the complete documentation index, see [llms.txt](https://jsverse.gitbook.io/transloco/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jsverse.gitbook.io/transloco/developer-tools/keys-manager-tkm/using-with-nx.md).

# Using with Nx 🐋

To use TKM in an Nx workspace, we are going to leverage the `--project` flag to dynamically set the base paths for `rootTranslationsPath`, `input`, and `output`, ensuring the correct translation files are handled for the specified project.

{% hint style="info" %}
Make sure you don't have these properties set on your `transloco.config.ts`
{% endhint %}

### Defining an Nx Workspace Task

To integrate Transloco commands with an Nx workspace, you can define tasks in the `project.json` file of each application or library where you want Transloco to extract or find keys. Below is an example setup:

```json
{
  "i18n-extract": {
    "command": "transloco-keys-manager extract --project projectName"
  },
  "i18n-find": {
    "command": "transloco-keys-manager find --project projectName"
  }
}
```

* **`i18n-extract`**: Extracts translation keys from the specified project.
* **`i18n-find`**: Identifies missing keys or extra keys in the specified project.

Replace `projectName` with the project's name as defined in your `angular.json` or Nx workspace configuration.

{% hint style="warning" %}
Don't pass the `cwd` option to these nx commands as it will affect the root path to look for the "prettier" config file used by the keys manager.
{% endhint %}

### Custom Output Paths with `${sourceRoot}` Interpolation

When using TKM in Nx monorepos, you might want to use a **single** `transloco.config.js` at the workspace root while customizing output paths per project. TKM supports `${sourceRoot}` variable interpolation in path configurations, which gets replaced with the actual source root of each project at runtime.

**Example configuration:**

{% code title="transloco.config.js" %}

```javascript
module.exports = {
  langs: ['en', 'fr'],
  keysManager: {
    output: '${sourceRoot}/../public/i18n',
    scopePathMap: {
      admin: '${sourceRoot}/../public/i18n/admin',
    },
  },
};
```

{% endcode %}

**Results in different paths per project:**

* For `apps/my-app` → `apps/my-app/public/i18n/en.json`
* For `libs/my-lib` → `libs/my-lib/public/i18n/en.json`

This allows you to maintain a centralized configuration while having translation files placed in custom locations for each project.

{% hint style="info" %}
The `${sourceRoot}` variable works in both the `output` path and `scopePathMap` values.
{% endhint %}

\\