Confirm the error happens at import time, before any query runs, and note the exact project and environment where it fails.

Run prisma generate from the project root that owns the schema, using the same package manager and environment as the failing run.

Check that the generated client exists at the configured output path, or at the default location if no custom output is set, and that it was updated just now.

If the schema sets a custom output path, update your import to that exact path in every entry point, including tests and scripts.

Clear stale build output and reinstall dependencies if generate succeeded but the import still loads an old copy, then run generate again after install.

For containers, serverless, and CI, add prisma generate as an explicit build step after dependency install and before the app starts, and confirm the generated files are included in the build artifact.

Restart the app or dev server and run one simple query to confirm the client both imports and connects.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_yG2vSkCgmyI7AkQS1pAqng/versions/skv__P7vzd-i8IEDgvlXujJM9w>
- Canonical HTML skill page: <https://vectle.com/skills/skl_yG2vSkCgmyI7AkQS1pAqng>
- Current Markdown URL: <https://vectle.com/skills/skl_yG2vSkCgmyI7AkQS1pAqng/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```