I know, that's my question

Oh, god. I was running

graphcool playground

instead of

graphql playground

.

Now I can see the left pane!

OH, wow, I'm slow.

graphql-cli

, not

graphcool-cli

. I'm blind

Okay, seems you both missed that 😄 Never mind, glad it works 😄

@agartha Is there any way to make it work with the standalone playground?

standalone?

It was actually a bit confusing when I initially read about

graphql-cli

- the

init

command starts a graphcool project, and uses many graphcool utilities (like the playground)

@Emi You should be able to just plug in the URL for your datamodel API

IE,

localhost:60000/app-name/stage

But you won't be able to see your datamodel and application API at the same time

Ok, it makes sense!

@agartha, I was referring to the Electron app.

You can just open the local folder in the Electron app

And you should get the same result

By the way, I also tested the yoga version of the playground. If I start with NODE_ENV=dev, I see the side bar, if I start without it, I don't

So still curious why that doesn't work for you

It works for me now. The issue was that I was running

graphcool playground

instead of

graphql playground

.

That still shouldn't be the issue

I (essentially) use

graphcool playground

(That is, I am using the beta version of graphcool, run

npm start

, then go to my app/stage's endpoint)

I've opened the folder with playground and it shows the left pane, but just with app (not database).

which shell are you running?

also what does your start script look like?

I'm on windows with CMD. This is my package.json: { "name": "my-app", "scripts": { "start": "cross-env NODE_ENV=dev node src/index.js", "playground": "graphcool playground" }, "dependencies": { "graphcool-binding": "1.3.5", "graphql-yoga": "^1.1.7" }, "devDependencies": { "cross-env": "^5.1.3", "graphcool": "1.0.0-beta4.1.1" } }

graphcool playground

will open the playground for your database API (the Graphcool server). That will never show your workspace panel on the left

it's the other way around

Really? As I said, when I run

npm start

then go to the API endpoint in my browser, it shows both

So it looks like we're all seeing different things?