Support for Apollo Sandbox (instead of Playground?)

[juergenzimmermann]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Apollo 2 was integrated with Playground which is retired since April 2020. Please see graphql/graphql-playground#1143.

Expected behavior

Apollo 3 is now offering Apollo Sandbox: https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development. There is ApolloServerPluginLandingPageDisabled and ApolloServerPluginLandingPageLocalDefault in the npm package apollo-server-core. It would be nice to have a config option for Apollo Sandbox.

What is the motivation / use case for changing the behavior?

Playground is retired since 1.5 years.

[rares-lupascu]

the only thing I did not get to work is the new subscription dependencies on "grahpql-ws" ... everything else is working for me in apollo studio running a local dev nestjs.

[kamilmysliwiec]

I just realized we haven't added a section on how to use Apollo Sandbox with the latest version, thanks for pointing that out!

Updated the docs https://docs.nestjs.com/graphql/quick-start#apollo-sandbox

Now, why this isn't turned on by default given that the graphql-playground is retired:

• as this is just a local dev IDE, there's no risk associated with this change
• Apollo Sandbox isn't compatible with browsers like Brave
• local development shouldn't require any external in-browser tools - using something built-in makes it way easier, especially for newcomers

We'll very likely migrate away and move to GraphiQL eventually, as recommended here graphql/graphql-playground#1143 (once it's stable etc).