In production with apollo-server-express 2.0.4 Playground is visible, with 2.0.0 is not.

REPRODUCTION HERE: https://brainy-spaghetti.glitch.me

With "apollo-server-express": "2.0.4" and NODE_ENV=production the Playground is visible.

With "apollo-server-express": "2.0.0" and NODE_ENV=production I have this: GET query missing.

Something is wrong?

[nderscore]

Confirmed the issue. Sorry for the confusion.

https://github.com/apollographql/apollo-server/blob/412be208c1b60c2f77333eec2840b64990ea7935/packages/apollo-server-core/src/playground.ts#L39

It’s likely due to the default value of {} for the playground config here.

[nderscore]

The default behavior of apollo-server’s integrated graphql-playground is for it to be disabled (along with introspection queries) when NODE_ENV=production.

This behavior can be over-ridden when you set the playground option in config.

In 2.0.0, the graphql playground could be enabled when NODE_ENV=production if you explicitly set the playground option to true, but provided no way to enable the playground with a custom config object.

In 2.0.2, this was adjusted to allow a custom config to enable the playground in production. Now, a truthy value will enable the playground, while a falsey value will disable it.

---

If you want to disable the playground in production while using a custom config in your local/development environment, you could do something like this:

const GRAPHQL_PLAYGROUND_CONFIG = {
  folderName: 'Foo',
  settings: {
    'editor.cursorShape': 'line',
    'editor.fontSize': 14,
    'editor.reuseHeaders': true,
    'editor.theme': 'dark'
  }
};

const server = new ApolloServer({
  playground: process.env.NODE_ENV === 'production' ? false : GRAPHQL_PLAYGROUND_CONFIG,
  schema: mySchema
});