Skip to content
LightNetLightNetLightNet
LightNet v4 is here! Learn how to upgrade your site

check-translations

The check-translations command is part of the LightNet CLI.

Terminal window
pnpm lightnet check-translations

Use this command to find translations that are still missing your site’s languages.

Run it from the root of your LightNet site project.

The command asks whether to run pnpm build for you. When you confirm, the build runs as part of the check and the translation results are read from that build.

Use it when you want to:

  • catch incomplete translations before deploying
  • review translation work after adding a new language
  • check inline translation maps after editing content or templates

Common checks

Section titled “Common checks”

Check translations:

Terminal window
pnpm lightnet check-translations

Run a build before checking translations:

Terminal window
pnpm lightnet check-translations --build

Check translations without running a build or showing a prompt:

Terminal window
pnpm lightnet check-translations --no-build

Skip completeness checks for specific translation keys (requires @lightnet/cli 4.9.0 or later):

Terminal window
pnpm lightnet check-translations --exclude ln.details.edit custom.title

You can also repeat --exclude to add more keys:

Terminal window
pnpm lightnet check-translations --exclude ln.details.edit --exclude custom.title

Options

Section titled “Options”
  • --build: runs pnpm build before checking translations.
  • --no-build: skips the build prompt and checks the latest available build output.
  • --exclude <keys...>: skips completeness checks for one or more space-separated translation keys. Repeat the option to exclude more keys. Matching is exact and case-sensitive; wildcards are not supported. Exclusions apply to built-in keys, custom keys, and inline translation-map paths. Stale override warnings are still reported for excluded keys.

If the command reports missing translations, add the missing values to the content or template that owns them.