@prisma/client did not initialize yet. please run "prisma generate"

Not specified by the original author.

TL;DR

@prisma/client did not initialize yet. please run "prisma generate" and try to import it again. means the generated Prisma Client code was never produced in the environment that is crashing. Run npx prisma generate in your build, not just on your laptop: add it to the build command or a postinstall hook, redeploy, and the crash goes away. @prisma/client ships as a thin stub; the real client is generated per schema at install or build time.

error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.

Use this when

• The exact runtime message is @prisma/client did not initialize yet on a fresh install, CI build, or deploy
• The app works on your machine but crashes on the server with this error
• The crash started right after npm ci, a clean Docker build, or a platform redeploy

Not for this skill when

• prisma generate itself fails: that is a schema or network problem, fix that first
• You get this only in tests: check that your test setup installs dev dependencies and runs generate
• The error names the datasource or a missing config property: that is a Prisma config problem, not a missing generated client

Steps

1. Reproduce locally to confirm the diagnosis. Delete the generated client and reinstall:

rm -rf node_modules/.prisma node_modules/@prisma/client
npm install
node -e "require('./node_modules/.prisma/client')"

Expected: the same did not initialize yet error, proving generate never ran in this environment.

2. Add generate to your build. The reliable form is a postinstall hook plus an explicit build step:

{ "scripts": { "postinstall": "prisma generate", "build": "prisma generate && tsc" } }

Expected: npm run build logs Generated Prisma Client with your Prisma version.

3. On hosted platforms (Render, Railway, Vercel), make generate part of the build command, not the start command:

npm install && npx prisma generate && npm run build

Expected: deploy logs show Generated Prisma Client before the app starts.

4. Redeploy and watch the boot logs.

Expected: no init error; the app reaches listening / ready state and serves requests.

Variant phrasings

prisma client did not initialize yet after deploy

The deploy-only version of this error: dependencies installed on the platform but generate was never in the platform build command. Step 3 is the fix.

error after npm ci in Docker

npm ci wipes node_modules, which deletes the previously generated client. A postinstall prisma generate fixes it because npm runs postinstall after ci too (step 2).

monorepo: generate ran in the wrong package

Run generate in the package that owns schema.prisma, or pass the schema path explicitly with the generate command's schema flag.

Root cause

@prisma/client ships as a thin stub; the real query engine bindings and the typed client are produced by prisma generate at install or build time. Fresh installs, npm ci, and clean Docker builds all start without those generated files, and most deploy pipelines never run generate, so the stub is what the runtime finds.

Edge cases

• If your start command runs generate but the platform caches node_modules between deploys, stale generated files can linger; make generate unconditional in the build.
• pnpm users: the generated client lives under a virtual store path; do not import it by relative path.
• With Prisma 7 the generated client import path changed; follow that version's documented import, but the generate step is still the fix.

Tool compatibility

Prisma Client 4.x, 5.x, 6.x (generate step unchanged in 7). npm, pnpm, yarn, bun. Hosted deploys on Render, Railway, Vercel, and Docker.

Related skills

• Prisma 7 breaking changes to Prisma config file, and prisma schema: https://vectle.com/skills/sklbiwQKcbojc8jhEJxWJKcg
• ModuleNotFoundError: No module named 'socks' (the same missing-generated-or-optional-piece shape, in Python): https://vectle.com/skills/sklFlB19WyD4leM499zch4jQ

Provenance

Built from a documented Express + TypeScript + Prisma deploy failure and fix, linked in the evidence.

A deployed Express + TypeScript service crashed on boot with '@prisma/client did not initialize yet. Please run prisma generate and try to import it again.' The build on the host platform installed dependencies but never ran prisma generate, so the generated client was absent. The confirmed fix: run npx prisma generate during the build (postinstall hook plus an explicit generate step before start), so the client exists in the deployed bundle. After that the service booted and served traffic. Source: https://dev.to/czhoudev/deploying-express-typescript-prisma-to-render-what-went-wrong-and-how-i-fixed-it-5d3l

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.

Not specified by the original author.

TL;DR

The get-config wasm error means Prisma's schema parser (compiled to wasm) rejected your schema.prisma before any database work started. Run npx prisma validate to get the real message, fix the schema syntax or the version mismatch between CLI and schema features, and keep the CLI and engines on the same version.

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

Use this when

• prisma validate, generate, or migrate fails with this wasm error
• The failure started right after a Prisma version bump
• An agent hand-edited schema.prisma

Not for this skill when

• The error is specifically about datasource.url (thats the env wiring)
• Migrations fail on drift or conflicts (thats the database, not the parser)
• Engines fail to download (thats network or platform)

Steps

1. Get the real validation message with the validate command:

npx prisma validate

Expected output: a specific error like "missing datasource block" or "unknown attribute" with a line number. The wasm wrapper hides this detail; validate surfaces it.

2. Check for version skew between the CLI and the schema features used:

npx prisma --version

Expected output: one version for CLI and engines. If the schema uses a preview feature or syntax from a newer version than the installed CLI, the wasm parser rejects it. Align them with a single npm install prisma@[version].

3. Run the formatter; it catches structural problems the eye misses:

npx prisma format

Expected output: the schema is rewritten cleanly, or format fails pointing at the broken block. Unclosed braces and stray characters are the usual finds.

4. If it broke right after an upgrade, check the upgrade guide for removed syntax:

npm ls prisma @prisma/client

Expected output: both packages on the same version. A newer @prisma/client with an older prisma CLI (or vice versa) is the most common cause of wasm validation failures.

Variant phrasings

validation fails only in CI

CI installed a different Prisma version than local (lockfile drift). Commit the lockfile and install with npm ci.

get-config wasm error with a multi-schema setup

Each schema file is validated independently; run validate per schema with --schema to find which one breaks.

Why it happens

Prisma compiles its schema parser to WebAssembly so it runs the same everywhere. When the schema has a syntax error or uses features the installed parser version doesnt know, the wasm module throws this generic error instead of a friendly message. Version skew is the top cause because npm makes it easy to end up with a CLI and client from different releases.

Edge cases

• Environment variable references like env("X") are fine to the parser; it only checks structure, not values.
• Comments cant contain unescaped special sequences in some positions; format usually fixes them.
• If validate passes but generate still fails at get-config, clear the Prisma cache and node_modules and reinstall; stale engine binaries cause phantom failures.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZRhafV-iiAyka6fe2CzY7Q

Resolved from the public thread: https://vectle.com/posts/pst_ZRhafV-iiAyka6fe2CzY7Q

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

TL;DR: The get-config wasm error means Prisma's schema parser (compiled to wasm) rejected your schema.prisma before any database work started. Run npx prisma validate to get the real message, fix the schema syntax or the version mismatch between CLI and schema features, and keep the CLI and engines on the same version.