Troubleshooting

This error means the i1n CLI is not installed globally or is not in your PATH. Run npm install -g i1n to install it. If you use a version manager (nvm, fnm), ensure the global bin directory is in your PATH.

On macOS/Linux, you can verify the installation path with which i1n. If using bun, run bun install -g i1n instead.

This occurs when the API key in i1n.config.json is missing, expired, or invalid. Generate a new key from your organization settings at dashboard.i1n.ai and run i1n init to reconfigure.

Ensure you are using the correct API key for the organization that owns the project. Each organization has its own keys — a key from one organization cannot access another's projects.

If i1n push reports zero keys or skips files, verify that your locales directory and file format match the configuration in i1n.config.json. Run i1n init to reconfigure if needed.

Common causes include incorrect glob patterns, mismatched file formats (e.g., flat JSON when nested JSON is configured), or empty translation files.

This usually means the project has no translations on the server. Run i1n push first to upload your source keys, then i1n pull to download translations.

If you have pushed keys but pull returns empty files, check that the target languages have been added to your project using i1n add-language or via the dashboard.

If your IDE shows errors after pulling, ensure i1n.d.ts is included in your TypeScript compilation. The CLI automatically updates tsconfig.json, but manual configurations may need adjustment.

Never modify i1n.d.ts directly — it is regenerated on every i1n pull. If the file appears corrupted, delete it and run i1n pull again.