Errorname / prisma-multi-tenant

🧭 Use Prisma as a multi-tenant provider for your application
MIT License
395 stars 45 forks source link

Cannot install prisma-multi-tenant, appears to have conflict with prisma/cli #80

Open Alwigi opened 3 years ago

Alwigi commented 3 years ago

I have prisma + prisma/client v2.25.0 installed and all is working fine against a Sql Server database. When installing prisma-multi-tenant using:

npm i -g prisma-multi-tenant

I get this in the terminal:

@prisma/cli@2.20.1 preinstall C:\Users\zzzzzzz\npm\node_modules\prisma-multi-

tenant\node_modules\@prisma\cli

node scripts/preinstall-entry.js

│     The package @prisma/cli has been renamed to prisma.                     
│                                                                             
│     Please uninstall @prisma/cli first.                                     
│     Then install prisma to continue using Prisma CLI:                       
│                                                                             
│         # Uninstall old CLI                                                 
│         npm uninstall @prisma/cli                                           
│                                                                             
│         # Install new CLI                                                   
│         npm install prisma --save-dev                                       
│                                                                             
│         # Invoke via npx                                                    
│         npx prisma --help                                                   
│                                                                             
│     Learn more here: https://github.com/prisma/prisma/releases/tag/2.16.0 

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @prisma/cli@2.20.1 preinstall: `node scripts/preinstall-entry.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @prisma/cli@2.20.1 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I have tried as below but the problem persists:

Any ideas?

avishwakarma commented 3 years ago

Any updates on this?