Troubleshoot build diagnostics

No messages were extracted

Confirm the file matches include/exclude, linguana() runs before React, and the content is literal visible JSX. Code blocks, hidden content, URLs, and opted-out subtrees are intentionally absent. Use t() or <T> for dynamic content.

Unsafe or ambiguous copy

The compiler skips machine-looking values and diagnoses mixed rich structures. Do not globally loosen the policy. Use data-translate for one literal custom attribute or named component slots for rich text.

Duplicate ID

Search every explicit use of the ID. Compatible repeated source is allowed; incompatible source must receive distinct IDs. Do not suppress this error because a catalog cannot map one ID to two meanings.

Strict build failed

Read the diagnostic code, severity, location, and remediation. If the candidate is an intentional conservative skip, use an object strict policy while fixing the corpus. Keep incompatible duplicates fatal.

Compiler runtime import cannot resolve

Transformed files import @linguanahq/react/compiler-runtime. Ensure the compiler and React runtime come from a compatible workspace/release and the bundler has not externalized only one package.

Verify

Run an extraction-only build, inspect .linguana/manifest.json, and run source-integrity checks. If the manifest is valid and the application builds without network access, compiler diagnosis is complete.

Next

For remote build failures, continue with Upload and authentication.