Multi-project playground no longer works (based on NODE_ENV=dev)
See original GitHub issueThis commit: https://github.com/graphcool/graphql-yoga/commit/a49583a
I don’t want to have to start 2 webservers to be able to do it now and in my opinion it’s a better option to educate the users instead of taking things away so you can’t do anything wrong.
i.e. one solution would be a (big) warning in the console if NODE_ENV
is set to dev
, which should never happen in production
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Multi-project playground no longer works (based on ...
Multi-project playground no longer works (based on NODE_ENV=dev) #125 ... You can still use GraphQL Playground by specifying the playground ...
Read more >node.js - Using NODE_ENV with multiple environments in ...
On a project that consisted of development, staging, and production (3 environments), I would usually set up my code to load configuration based...
Read more >Migrating to Apollo Server 4
In Apollo Server 4, expressMiddleware no longer supports Connect. An interested developer could build a Connect-specific middleware, and a PR to this migration ......
Read more >Environments · Cloudflare Workers docs
The Workers platform allows you to create and manage different environments. Through environments, you can deploy the same project to multiple ...
Read more >webpack/webpack - Gitter
ERROR in NormalModuleFactory.beforeResolve is no longer a waterfall hook, but a bailing hook instead. Do not return the passed object, but modify it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
maybe allow users to pass playground options / extend the playground options
There are two main reasons for this change:
NODE_ENV
todev
in production. (We’ve actually seen this happening a couple of times now.)That being said, we’ll look into ways how we can simplify this going forward. Do you have a concrete design suggestion on how to accomplish this?