I’m having an issue with using prisma deploy with ...
# orm-helpw
wontwon
10/22/2018, 7:05 PMI’m having an issue with using prisma deploy with the graphql-cli. Here’s what I’m doing: -Set up new graphql app via graphql-cli, run prisma init to add a heroku hosted prisma server. When I run prisma deploy, I get a “mutiple graphql version error”
wontwon
10/22/2018, 7:05 PMI’m just following a tutorial I saw on youtube where the individual teaching how to setup prisma with heroku basically replaced the endpoints in their graphql application with the heroku endpoints
y
yolen
10/22/2018, 7:08 PMI had the same problem yesterday. solution was to add this to package.json
Copy code
"resolutions": {
"graphql": "^0.13.2",
"**/graphql": "^0.13.2"
},yolen
10/22/2018, 7:08 PMother solutions found on the web did not work for me
h
Harshit
10/22/2018, 7:08 PM@wontwon @yolen solution will only work if you use yarn I guess
y
yolen
10/22/2018, 7:09 PMyes sorry. I use yarn. As I understood previous problems with mutiple graphql the they only occur when using yarn; not npm?
h
Harshit
10/22/2018, 7:11 PMFor now you can specify version of graphql to be 0.13.2 in you package.json I guess and then nuke node_modules and npm install, or if you a happy yarn user like I and @yolen do the resolutions thing
Harshit
10/22/2018, 7:11 PMIt is a weird deps issue we face many time for packages like graphql who maintain semver differently, not really a fault of prisma team 😐
Harshit
10/22/2018, 7:14 PM@yolen This do occur in npm if a package do not follow semver properly, this fix for npm is that pin version in package.json or manully delete conflicting one from node_modules, I ran into this many times when using apollo in a monorepo, kinda bummer
Harshit
10/22/2018, 7:15 PMI really dont understand why some packages choose minor version bump as a mean of introducing breaking changes and causing these issues
w
wontwon
10/22/2018, 7:45 PMthanks guys
🙌 1
wontwon
10/22/2018, 7:45 PMmuch appreciated
🙂 1
3 Views