Open martinez-hugo opened 10 months ago
Have you ran npm install?
Yes Hugo MartinezLe 31 déc. 2023 à 16:20, Jordan Harband @.***> a écrit : Have you ran npm install?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
You have a node_modules inside src, but src is inside another node_modules, which doesn’t make sense.
It’s normal in case of usage of turbo I think Because in case of using Turbo, workspaces are considered as pkgHugo MartinezLe 31 déc. 2023 à 16:25, Jordan Harband @.***> a écrit : You have a node_modules inside src, but src is inside another node_modules, which doesn’t make sense.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Sounds like an issue with turbo then, which I’m not familiar with.
I'm assuming you are using TurboRepo. https://turbo.build/repo/docs/handbook/tools/prisma
We are facing similar issue with npx -y rimraf on some particular directories, its not case-sensitive file system.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When I run any prisma command, I have this error :
Expected Behavior
No response
Steps To Reproduce
A monorepo managed with turbo My workspace that use prisma is src
prisma deps is added as dev dependency in src package.json file
And so I run npx prismaor npx prisma generate in src directory and that's not works
Environment
@lareservetech:registry = "https://npm.pkg.github.com/" @LaReserveTech:registry = "https://npm.pkg.github.com/" @martinez-hugo:registry = "https://npm.pkg.github.com/" //npm.pkg.github.com/:_authToken = (protected) engine-strict = true
; node bin location = /usr/local/bin/node ; node version = v20.10.0 ; npm local prefix = /Users/hugomartinez/veille-360 ; npm version = 10.2.5 ; cwd = /Users/hugomartinez/veille-360 ; HOME = /Users/hugomartinez ; Run
npm config ls -l
to show all defaults.