Prisma Client removed on adding a new package: Error: @prisma/client did not initialize yet

[divyenduz]

This behavior can be observed in both npm and yarn, setup a Photon project and run any query with photon to ensure that it exists.

Now add any dependency in yarn, npm and re-execute photon query. I reproduced this with yarn add dotenv or npm install dotenv.

It doesn't matter if dotenv is already install or is a new package. I could reproduce this reliably.

You would run into (error paraphrased):

npm: import { Photon } from '@prisma/photon' no found.
yarn: Photon is not initialized yet. Please run prisma2 generate again

I used the following versions:

divyendusingh [prisma]$ yarn --version
1.21.1
divyendusingh [prisma]$ npm --version
6.10.2

[timsuchanek]

I can't reproduce this with npm@6.13.4 and yarn@1.21.1.

[divyenduz]

I could reproduce this once today. But not anymore afterwards. I would love to keep this in the next sprint as I think it is important and try to find a reproduction.

[divyenduz]

Tim has a reproduction of a different error of similar nature now. I will look for a related reproduction of the actual error "Photon is not initialized yet. Please run prisma2 generate again" but Tim can already start on the other bit of it.

[divyenduz]

"Photon is not initialized yet. Please run prisma2 generate again" this is also observable on Heroku. Might be related, will create a separate issue, if needed.

[timsuchanek]

I created a reproduction attempt in https://github.com/timsuchanek/photonjs-390. But just an attempt. Unassigning myself until we have a reliable reproduction.

[pantharshit00]

I am also unfortunately unable to reproduce this.

[divyenduz]

I am also unable to reproduce this with a local package like in Tim's repo. I tried that and its file variant (referring to prisma-client by its folder).

[janpio]

Note: Update issue title and description to new output.

[Zhomart]

There is prisma/prisma#2106 similar discussion going. I had similar issue, but it was my own fault adding **/node_modules/** to ignore field in firebase.json.

UPDATE: false alarm, use yarn instead of npm. You can still ignore node_modules.

[Jolg42]

@janpio I created this issue for the Firebase problem #732

[deadcoder0904]

I got this error Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again. when I updated Prisma to v2.2.0

[janpio]

Can you open a new issue pls @deadcoder0904? Thanks.

[deadcoder0904]

I think I opened in wrong repo 🤦‍♂️ prisma/prisma#2963

[janpio]

All good. Thanks.

[nargetdev]

@deadcoder0904 same here - exactly when I upgraded to "@prisma/client": "2.2.0" (which was necessary to fix a different bug within prisma up from 2.1.0)

[deadcoder0904]

@nargetdev did you solve it? if not, here's the solution :)

[MichaelGorski]

I am getting this error. Couldn't find any workarounds yet.

My dependencies

  "dependencies": {
    "@prisma/client": "^2.6.2",
    "apollo-server": "^2.17.0",
    "body-parser": "^1.19.0",
    "connect": "^3.7.0",
    "cors": "^2.8.5",
    "dotenv": "^8.2.0",
    "express": "^4.17.1",
    "faker": "^5.1.0",
    "firebase-admin": "^9.1.1",
    "nexus": "^0.26.1",
    "nexus-plugin-prisma": "^0.18.1",
    "uuid": "^8.3.0"
  },
  "devDependencies": {
    "@babel/cli": "^7.11.6",
    "@babel/core": "^7.11.6",
    "@babel/node": "^7.10.5",
    "@babel/preset-env": "^7.11.0",
    "@prisma/cli": "^2.6.2",
    "@types/node": "^14.6.4",
    "cross-env": "^7.0.2",
    "nodemon": "^2.0.4",
    "ts-node": "^9.0.0",
    "ts-node-dev": "^1.0.0-pre.62",
    "typescript": "^4.0.2"
  },

[sreuter]

@MichaelGorski You should remove your @prisma/cli and @prisma/client dependencies from your package.json and delete your node_modules (and yarn.lock if you use yarn) and install things fresh again.

That being said, I'm getting the same error right now, even tho I don't have those in my package.json.

[MichaelGorski]

Solved it
Somehow when I installed nexus, my dependencies were bugged and it installed @prisma/client as a dependencie like @prisma/cli.

My Solution:
Remove all related dependencies, delete node_modules. Install it clear. Remove all related prisma/nexus files from your project.
Add nexus, run nexus dev. You should get a warning with empty Graphql etc.. Then move all the files back to api/graphql, add nexus-plugin-prisma, run nexus dev and it should work again.

@sreuter Did you try my solution? It worked for me

edit: grammar

[sreuter]

Thanks @MichaelGorski.. For me it was something else in case somebody still has problems:

I had to remove output = "./generated/client" from my schema.prisma (which was a left over from using the client directly before nexus), so npx prisma generate actually creates the client in the right location.

[talentlessguy]

Happens with pnpm 5.6 and node 14.8

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

even though the client is already generated

doesn't work with yarn 1.22.5 either

even tho the client exists:

➜ ls node_modules/@prisma/client
 generator-build   node_modules   runtime
 index.d.ts        package.json   scripts
 index.js          README.md     

[pantharshit00]

@talentlessguy Client is not generated at that location now, please check node_modules/.prisma

[talentlessguy]

@pantharshit00 there's this:

➜ ls node_modules/.prisma/client
 index.d.ts   index.js   package.json   query-engine-debian-openssl-1.1.x   schema.prisma

[jdevng]

My environment is setup with a prisma2 directory and an apollo2 directory. The prisma directory is setup connected to MySQL. Commands invoked from the CLI write and read to/from the database.

I am attempting to load Prisma Client for use in Apollo2. I am in the Apollo directory, and add the dependency for prisma client using the following:

npm install "@prisma/client" --save-dev

I added the following code to my index.js for Apollo:

import { PrismaClient } from '@prisma/client';
const prisma = new PrismaClient();

I get the following error:

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

No idea what this means, I wouldn't assume a dependency would need to be 'initialized', but I assume it's trying to build code from my schema. So I run

% npx prisma generate --schema ../prisma/hello-prisma/prisma/schema.prisma

which points to my prisma schema I had setup previously, I'm assuming this is used to generate the client code. It completes without error.

When invoking apollo, I get the same generate error. So I run the following:

% prisma generate
 ▸    Couldn’t find `prisma.yml` file. Are you in the right directory?

How do I set this up so that Apollo can load in the PrismaClient?

Dependencies:

"devDependencies": {
    "@prisma/cli": "^2.8.0",
    "@types/node": "^14.11.2",
    "ts-node": "^9.0.0",
    "typescript": "^4.0.3"
  },
  "dependencies": {
    "@prisma/client": "^2.8.0"
  }

[Jolg42]

Hi @jdevng!

Your output here

% prisma generate
 ▸    Couldn’t find `prisma.yml` file. Are you in the right directory?

looks like Prisma 1 output, to avoid this you could run npx like this npx @prisma/cli generate or install it globally npm i -g @prisma/cli

[srikanthkyatham]

Hi @jdevng!

Your output here

% prisma generate
 ▸    Couldn’t find `prisma.yml` file. Are you in the right directory?

looks like Prisma 1 output, to avoid this you could run npx like this npx @prisma/cli generate or install it globally npm i -g @prisma/cli

If the above advise would have mentioned in the output, it would be more helpful.

[Jolg42]

@srikanthkyatham It's something we want to improve indeed! 😃

[samrith-s]

Hey. I am trying to deploy my lambda function which used Prisma 2. I was directed to this issue with from the error.

I currently do:

prisma generate

And then package everything.

In my package, I have a node_modules folder. Which has all of the prisma stuff:

Is something missing? Coz I get this error when trying to run my lambda:

[Jolg42]

Context for @samrith-s comment's #390 (comment)
Minimal reproduction https://github.com/samrith-s/nestjs-prisma-serverless-error
https://prisma.slack.com/archives/CKQTGR6T0/p1609623950269000

[samrith-s]

I had a chat with @ryands17 and he advised me to include @prisma/cli to the build. Now my package size rose from 7MB to 59MB! Is there any way to reduce this? Coz this is eating up on my deployment time massively.

[Jolg42]

@samrith-s in your case you could remove the @prisma/cli and generate the Prisma Client in a custom folder that you include when doing the deployment.
See https://www.prisma.io/docs/concepts/components/prisma-client/generating-prisma-client#specifying-a-custom-output-path
Does that work for you?

[samrith-s]

@Jolg42 yeah I tried that. But I still need to manually pack the rhel-open-ssl binary with lambda which isn't done at all in the example.

I have so much boilerplate code just to make the query engine available to Prisma, have no idea how it works in the SLS Lambda example here: https://www.prisma.io/docs/guides/deployment/deploying-to-aws-lambda

[Jolg42]

@samrith-s Could you maybe create a new issue about that with your boilerplate code?

[NickSchmitt]

Once I get to npm run dev at the beginning of the Prisma Quick Start Tutorial, I receive an error that tells me to report here:

Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.
In case this error is unexpected for you, please report it in https://github.com/prisma/prisma-client-js/issues/390.

Upon running prisma generate I receive zsh: command not found: prisma

[Jolg42]

Note: discussion from previous comment is there prisma/prisma#4978