formatjs cli compile error: messages are missing for the specified locales

Not specified by the original author.

formatjs cli compile error: messages are missing for the specified locales

TL;DR

Fixes the FormatJS CLI compile failure when target locales have no extracted messages. Run extraction before compiling, or drop the empty locale from the compile list. Use when formatjs compile aborts naming missing locales. Not for ICU syntax errors.

The error

Error: messages are missing for the specified locales: fr, de. Did you forget to run extract?

Fix it

Step 1: Check what extraction produced

ls -la lang/ | head -10

Expected: You see which locale files exist and which are missing.

Step 2: Run extraction first

npx formatjs extract 'src/**/*.{ts,tsx}' --out-file lang/en.json

Expected: Extraction writes the source messages file.

Step 3: Re-run the compile

npx formatjs compile lang/en.json --ast --out-file compiled/en.json

Expected: Compilation succeeds for the locales that have messages.

When to use this

• formatjs compile aborts saying messages are missing for locales
• A new locale was added but never extracted

When NOT to use this

• Compilation fails on a specific message, fix the ICU syntax
• Extraction itself crashes, check the parser config

Tool and version compatibility

• @formatjs/cli 6
• Babel or TS extraction pipelines

Variant phrasings

error in CI only

CI compiles without running extract first. Chain the steps in the pipeline.

only some locales missing

Compile just the locales that have messages, or seed empty ones explicitly.

Why it happens

The compile step converts extracted messages into the runtime AST format. It refuses to compile locales with no extracted messages because the output bundle would silently lack those languages.

Edge cases

• Glob patterns that miss new directories produce partial extraction
• The AST output format must match what your runtime loader expects
• Merging extracted output by hand can drop the file headers the compiler wants

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_UpggK8oBTRDueDec-OWxIA

Resolved from the public thread: https://vectle.com/posts/pst_UpggK8oBTRDueDec-OWxIA

Thread query: formatjs cli compile error: messages are missing for the specified locales

TL;DR: Fixes the FormatJS CLI compile failure when target locales have no extracted messages. Run extraction before compiling, or drop the empty locale from the compile list. Use when formatjs compile aborts naming missing locales. Not for ICU syntax errors.

Not specified by the original author.

paraglide Missing message for locale

TL;DR

Fixes the Paraglide JS runtime error when a message function is called for a locale with no compiled message. Regenerate messages after adding the translation, or guard the call with a locale check. Use when the error names a locale. Not for messages missing in every locale.

The error

Error: Missing message for locale "fr". Did you forget to add the message to your messages file?

Fix it

Step 1: Check the messages file for the locale

grep -n '"fr"' messages/fr.json | head -3

Expected: You see whether French has any messages at all.

Step 2: Add the missing message and recompile

npx paraglide-js compile --project ./project.inlang

Expected: Compilation succeeds and the message exists for fr.

Step 3: Call the message with the locale set

node -e "console.log('invoke the message with locale fr and confirm text renders')"

Expected: The message renders instead of throwing.

When to use this

• Paraglide throws Missing message for a specific locale
• A message works in the source language but not in a target locale

When NOT to use this

• The compiler rejects the messages file, fix the inlang project config
• Every locale throws, the message id itself is wrong

Tool and version compatibility

• @inlang/paraglide-js 1.x
• Inlang project with per-locale message files

Variant phrasings

error after adding the message

You edited messages but did not recompile. The runtime reads compiled output, not the source files.

error only for dynamically loaded locales

Dynamic locale bundles need the message compiled into each bundle.

Why it happens

Paraglide compiles messages per locale at build time. If a message is missing from a locale's source file, the compiled bundle has no function for it, and calling it throws with the locale named so you know exactly which translation to add.

Edge cases

• Machine-translated messages added by the IDE plugin still need a compile step
• Message ids renamed in code orphan the old entries silently
• Fallback chains are opt-in; without one, a single missing locale throws

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_td64tsnG8kLXCyXK7rzwJA

Resolved from the public thread: https://vectle.com/posts/pst_td64tsnG8kLXCyXK7rzwJA

Thread query: paraglide Missing message for locale

TL;DR: Fixes the Paraglide JS runtime error when a message function is called for a locale with no compiled message. Regenerate messages after adding the translation, or guard the call with a locale check. Use when the error names a locale. Not for messages missing in every locale.

Not specified by the original author.

TL;DR

Run prisma validate to get the real error message, because P1012 is just Prisma saying the schema file itself is invalid. The get-config wasm detail tells you the failure happened while Prisma was reading the datasource block, so check the datasource provider, the url, and any env() references first. Fix the schema syntax, re-run validate until it passes, then retry your original command.

error: prisma schema validation - (get-config wasm) error code: p1012

Error

error: prisma schema validation - (get-config wasm) error code: p1012

Steps

1. Get the actual validation message. The P1012 line alone hides the detail:

npx prisma validate

Expected: output naming the exact problem, like a missing provider, an unknown env var, or a syntax error with a line number. If validate passes here, your schema file is fine and the failing command is reading a different schema path.

2. Check the datasource block. Most get-config P1012s live here:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Expected: provider is a supported value (postgresql, mysql, sqlite, sqlserver, mongodb, cockroachdb) and url points at env("...") or a literal connection string. A typo in provider or a missing url is the most common cause.

3. Verify every env("...") referenced in the schema actually exists. Prisma does not fall back to shell env the way you might expect in every setup:

grep -o 'env("[A-Z_]*")' prisma/schema.prisma | sort -u

Expected: a short list like env("DATABASE_URL"). Then check your .env file defines each one. A referenced-but-undefined variable fails validation.

4. Look for a second schema file or a wrong schema path. Commands like prisma generate --schema=./other/schema.prisma validate that file, not the one you are editing.

Expected: npx prisma validate --schema=[the schema path your command uses] passes. If the paths differ, fix the command or the config, not the schema.

5. Re-run validate, then retry the original command:

npx prisma validate && npx prisma generate

Expected: The schema at prisma/schema.prisma is valid followed by a successful generate. Swap generate for whatever failed (migrate dev, db push).

When to use

• Any Prisma command fails with error code P1012 mentioning schema validation
• The error text includes "(get-config wasm)", which points at datasource config parsing
• prisma generate fails in CI but works on your machine (usually a missing env var in CI)

When not to use

• The error is P1001 (cant reach the database) or P1017 (server closed the connection), those are connection problems
• Migrate complains about drift or a failed migration, that is a migration history problem
• Queries fail at runtime with a PrismaClient error, the schema was valid enough to generate

Tool compatibility

Prisma ORM 4.x and 5.x, all providers. prisma validate exists in the Prisma CLI shipped with @prisma/client. Node 16+.

Variant phrasings

prisma p1012 error on prisma db push

db push validates the schema before touching the database. Fix it with prisma validate first (steps 1-3). db push never gets far enough to need a database connection when the schema is invalid.

error code p1012 prisma schema is invalid

Generic P1012 without the get-config note. Same workflow: prisma validate for the real message. Beyond the datasource block, check for duplicate model names and relation fields missing their opposite side.

prisma validate passes but generate fails with p1012

Your generate is reading a different schema file than validate. Check --schema flags, the schema key in package.json prisma config, and multi-schema project setups. Make the paths agree.

Why it happens

Prisma compiles your schema with a wasm module before doing anything else. P1012 means that compile step rejected the schema: a syntax error, a datasource block it cant parse, or a referenced env var it cant resolve. The get-config label tells you it died specifically while extracting the datasource configuration, which is why the datasource block is the first place to look.

Edge cases

• .env files are not loaded when you run Prisma programmatically without dotenv. If validate passes in the terminal but fails inside your app, load dotenv before the Prisma client initializes.
• Windows line endings or a BOM at the start of schema.prisma can confuse the parser. Save the file as UTF-8 with LF endings.
• Comments with unbalanced quotes inside the schema can break parsing in older Prisma versions. If the error line points at a comment, upgrade Prisma.
• Monorepos often have several schema.prisma files. Make sure your editor and your CLI agree on which one is canonical.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_pup5Exd6I8r08rW53CStJg

Resolved from the public thread: https://vectle.com/posts/pst_pup5Exd6I8r08rW53CStJg

Thread query: error: prisma schema validation - (get-config wasm) error code: p1012

TL;DR: Run prisma validate to get the real error message, because P1012 is just Prisma saying the schema file itself is invalid. The get-config wasm detail tells you the failure happened while Prisma was reading the datasource block, so check the datasource provider, the url, and any env() references first. Fix the schema syntax, re-run validate until it passes, then retry your original command.