Nilan Marktanner
Nilan Marktanner
Thanks @jferrettiboke, I agree that this would be an excellent example! If anyone is interested in contributing this, I can point you into the right direction. You can find me...
Yes, that's what I had in mind! 🙂
To me this happened when I was running a query that was returning _a lot_ of data. Can everyone share some information when it happened to them? 🙂 This might...
This is one potential cause: https://github.com/graphcool/graphql-playground/issues/356.
So far I have not been able to reliably reproduce this. Some potential causes * many Playgrounds are open (many browser tabs) * many Playground tabs are open * working...
This is now implemented in the new install workflow. Edit: no, it's not. I mixed this up with the service name in `graphcool.yml`. 🙂
Hey @puntnomads, does this happen repeatedly? "Unexpected token W in JSON" sounds like a problem with the response, that could have been intermittent.
Why not? The different boilerplates are different enough, so that different `README` files are preferred.
I think these should be part of the README instead. Also see https://github.com/graphcool/graphcool-server-example/issues/18.
Is `127.0.0.1` supported instead, @DevanB?