Prisma

does anyone have weird issues upgrading versions of the beta cli?

I’m using yarn and on a mac with node installed through homebrew. I have a couple issues but the one that i cant get passed is `this.client.getDeployUrl is not a function`

i had a similar issue, i had to make sure i was using a later version of node. right now i am node 8.6. i also did a complete reinstall of the graphcool client. `npm remove graphcool` `npm install -g graphcool@next`

hmm, ive tried removing and adding graphcool a couple times now

i seem to be able to run other commands (diff, info, list)… just not deploy

```graphcool version
graphcool/0.7.0-beta.6 (darwin-x64) node-v8.6.0
```

yeah that is the version i am running as well

i feel like i had this issue yesterday too, but somehow got past it

then i upgraded to the newest beta and :boom:

i tried going back too, but no luck :sadparrot:

i think i can still use the ui though… so ill manually deploy stuff for now

no worries, im sure it will all get sorted out eventually. I appreciate the attempt though!

actually have you tried the deeper debug?

i did, but didnt quite understand the output. it looked like it authenticated fine. ill post that

```  yaml Getting definition from cache +0ms
  yaml Getting definition from cache +1ms
  bundler bundling +479ms
  bundler emptied .build +3ms
  bundler copied files +13ms
  bundler compiled typescript +449ms
  bundler generated env files +0ms
  bundler generated handler files +2ms
  bundler zipped +51ms
TypeError: this.client.getDeployUrl is not a function```

i can add more ill just have to censor some of the output

having the same issue on windows with the same versions of graphcool and node... it started when i added the template auth/email-password.  if i comment those resolver function declarations out of graphcool.yml i can deploy without the error

<@U4RMC6JF5> @eli my apologies! That was a bug in the @next, a new version is available that is working!