https://www.prisma.io/ logo
Join Slack
Powered by
oh wait, its inside `@prisma` , the runtime folder...
# orm-help
d
oh wait, its inside 
@prisma
, the runtime folder is exist, but not the 
findSync
r
@David 👋 Could you explain your use case for importing these functions?
d
Hi @Ryan , Nice to see you again. Actually I am not the one want to import them, I got an error when build my app. So when I see the error, I check it, the error occurred in 
node_modules/.prisma/client/index.js:55
and I check its imported from 
@prisma/client/runtime
. But when I go there, the function isn't exist.
r
Are you on the latest version of Prisma? Also what’s the command you’re using to build your app?
d
Copy code
"dependencies": {
    "@prisma/client": "2.21.0",
    .....
},
"devDependencies": {
    "prisma": "^2.21.0",
     ....
}
my command to build is: 
_"build"_: "yarn -s run clean && yarn -s run generate && tsc"
while: 
"clean": "rm -rf node_modules"
and 
"generate": "prisma generate"
r
Was it working before you had updated anything? If not, then I would like to check this.
d
ok, actually I kinda feel confused too. earlier it's work and I don't remember change anything in my code. (but maybe I re-doing npm install or something after that, but I forgot it) and when I build it again, this issue appear.
r
Could you run 
npm ci
and check if it works again?
d
Because I am working with rushjs and its mainly execute yarn and don't create 
package-lock.json
which is make it not working with 
npm ci
. Is it okay for me to use 
yarn install --frozen-lockfile
?
r
Removing 
node_modules
then installing 
yarn --frozen-lockfile
.
d
rm -rf node_modules/ && yarn install --frozen-lockfile
ok im trying now
will update you soon Ryan, thanks.
👍 1
no it's not work 😕
r
Then it seems that the packages are changed, as it was working before.
d
@Ryan is it from the repository in NPM?
r
No, possibly the versions were updated in your repo
d
you mean the version from package.json in my repository? i recheck with main, and the version still same hmm. or should i downgrade the version?
😄
r
If it was working before, then try checking if 
yarn.lock
was changed or not.
d
hmm I don't see any modified status from git to 
yarn.lock
file
r
Ohh, that’s strange 😅
@janpio any idea probably?
d
my reaction also "😅" when I got this issue. btw thanks for your help @Ryan , really appreciate it. Let's wait for @janpio, maybe he have any idea about this. 🙂
🙌 1
j
What does your 
npx prisma -v
output look like?
d
Copy code
prisma               : 2.28.0
@prisma/client       : 2.23.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 89facabd0366f63911d089156a7a70125bfbcd27 (at ../../common/temp/node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine     : migration-engine-cli 89facabd0366f63911d089156a7a70125bfbcd27 (at ../../common/temp/node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 89facabd0366f63911d089156a7a70125bfbcd27 (at ../../common/temp/node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary        : prisma-fmt 89facabd0366f63911d089156a7a70125bfbcd27 (at ../../common/temp/node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash : 89facabd0366f63911d089156a7a70125bfbcd27
Studio               : 0.417.0
Preview Features     : orderByAggregateGroup
wait, how can the client and prisma itself be different when in the 
package.json
it's have same version.
Hi @Ryan, @janpio, thanks for your help, I already resolved this issue. It's because somehow there is a new script added in our repository, which is will auto run when we are commit, and one of the script lines is to update the library (and sadly the prisma is updated globally, which is not detected by our check earlier in this thread discussion), this is what make the 
prisma
and 
@prisma/client
library is have different version. and the version mismatch create the issue. no wonder it's working fine and then after that it's become broken. the script is got into my development branch because one of our local config to always merge 
main
branch into our in dev branch.
💯 2
r
Awesome!
🙌 1
4 Views
Open in Slack
PreviousNext
Powered by