This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
Cannot find module '@prisma/client' after installing a new package via NPM #560
Labels
Milestone
Comments
Jolg42
added
bug/1-repro-available
A reproduction exists and needs to be confirmed.
kind/bug
A reported bug.
labels
Mar 11, 2020
This comment has been minimized.
This comment has been minimized.
Can reproduce:
|
What is probably happening is that generate uses yarn later the npm install does not pick up and thus remove the @prisma/client from that |
matthewmueller
added
bug/2-confirmed
We have confirmed that this is a bug.
and removed
bug/1-repro-available
A reproduction exists and needs to be confirmed.
labels
Mar 11, 2020
Possible reason: #561 |
Jolg42
added a commit
to prisma/prisma
that referenced
this issue
Mar 17, 2020
…e npm by default, use yarn only if there is a yarn.lock
I think you wanted to close this as well with your commit message @Jolg42 |
Yes indeed I also wanted to post this: fixed in alpha 920! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Steps to Reproduce
0. Install packages
0.5 Add tsconfig.json
This is a cleaned up result of running
./node_modules/.bin/tsc --init
and changing thetarget
field.1. Start with a working prisma schema
This step can be anything, but here's mine:
2. Run
./node_modules/.bin/prisma2 generate
, get a working clientYou should see
3. Write a script that uses
@prisma/client
Again shouldn't matter but here's mine:
All good.
4. Run
npm install uid
(or any package name)$ npm install uid + uid@1.0.0 removed 8 packages, updated 124 packages and audited 173 packages in 3.894s
NPM version
Node version
5. Run your script again
To fix this, you need to run
./node_modules/.bin/prisma2 generate
again. This is really disruptive.The text was updated successfully, but these errors were encountered: