eloqnt/studiov0.5
Navigation

Quickstart

Install eloqnt/cli and lint your project.

Use your agent

Get started in seconds by letting your coding agent take care of the setup:

Manual setup

Install the CLI

Add the CLI as a local project dependency:

npm install @eloqnt/cli --save-dev

If you're in a monorepo, install it within local packages as needed.

Add a config file

Create a config file at .eloqnt/config.ts:

.eloqnt/config.ts

import {defineConfig} from '@eloqnt/cli';
export default defineConfig({
// The folder containing your source code
// (optional, only if you use next-intl)
srcPath: './src',
// Where and how you store your messages
messages: {
path: './messages',
locales: 'infer',
sourceLocale: 'en',
format: 'json'
}
});

All paths are relative to your project root.

For more sophisticated setups like monorepos or when not using next-intl, please see the configuration docs.

Lint your source code and messages

Lint your project for common errors like missing translations, unused messages, broken ICU arguments and more:

npx eloqnt lint

This runs static analysis on your source code and matches it against your messages.

See eloqnt lint for details.

Start translating

Once linting works, you can optionally use eloqnt translate to fill in any missing translations:

eloqnt translate
Context enrichment complete
Translated es via eloqnt/engine (hosted)
Post-translation checks done
messages/
es.json 1 translated
✔ Project fully translated

To get started with translating, log into eloqnt/studio first: