i18n.yml already exists; use --force to overwrite
Your project already has a configuration. Open i18n.yml and update its locales, paths, or provider settings, then preview with hyperlocalise run --dry-run.
If you deliberately want to replace it with a starter, save a copy first, then run hyperlocalise init --force. This overwrites the existing configuration. See Configure your project.
sync requires top-level "hyperlocalise" or "storage.adapter"
Choose the destination before adding configuration:
- For Hyperlocalise Platform, add the top-level
hyperlocaliseblock from Connect the CLI. - For experimental TMS entry sync, add
storage.adapterand the provider’sstorage.config. See TMS integrations. - For provider file operations, use the provider command family, such as
crowdinorphrase, with its own configuration.
hyperlocalise and storage are configured, Platform takes precedence. Use separate config files when you need both destinations.
unsupported output format
Cause: wrong --output value.
Fixes:
status: onlycsvsync:text,json, ormarkdown(also acceptsmd)
unsupported file extension during run
Cause: a mapped source or target file uses an extension not supported by the local parser.
Fixes:
- use one of:
.json,.jsonc,.yaml,.yml,.js,.jsx,.mjs,.cjs,.ts,.tsx,.mts,.cts,.properties,.ini,.xml,.resx,.resw,.arb,.xlf,.xlif,.xliff,.po,.html,.liquid,.md,.mdx,.adoc,.asciidoc,.asc,.strings,.stringsdict,.xcstrings,.csv,.tsv,.toml,.ftl,.srt,.vtt,.sbv,.svg - verify bucket
fromandtopaths resolve to the expected file names
.xcstrings, ensure the catalog has a strings object and either a source-language localization for variant/substitution entries or simple catalog keys that can be used as source text.

