Unable to connect to graphqlhub.com
See original GitHub issueHello, I was trying out ReactQL today and after installing all dependencies and loaded the browser for the first time, i was met with this error in the console:
FetchError: request to https://graphqlhub.com/graphql failed, reason: connect ECONNREFUSED
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
GraphQL Playground - Apollo GraphQL Docs
Sandbox automatically attempts to connect to a GraphQL server running at http://localhost:4000 . You can use the box at the top of the...
Read more >Top GraphQL Errors and How to fix them
When there is a network error while trying to contact a GraphQL server, due to either the ... websocket connection could not be...
Read more >graphql-go/graphql - Gitter
I've seen graphql-go/graphql in production use and it's capable of ... I am looking to do something similar to https://graphqlhub.com , where they...
Read more >Fail to connect to GraphQL API server - react native
I found the solution, the SSL installed on the server was invalid so I had to use Free Let's Encrypt SSL and worked...
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 FreeTop 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
Top GitHub Comments
There are so many interesting projects out there since creating this starter kit, that it really depends what you’re trying to achieve.
For a general React framework, I’d probably go with NextJS. Hard to argue with the funding and commercial support being ploughed into it. It’s also a first target for React Server, which makes it more interesting to me. There’s a far higher likelihood the framework will be supported and upgraded vs. a solo-author starter kit like ReactQL.
For bolting on GraphQL, I’d choose either Url or Apollo on the client side. I tend to write GraphQL servers in Rust or .NET these days, but Apollo Server is an obvious choice for JS.
I use GraphQL Code Generator for generating types.
Beyond that, there’s a bunch of interesting new libs. If you’re doing a lot of DB access and want to build a GraphQL server on top of it, Prisma looks like a good JS choice with some commercial backing. I haven’t used it in a project, so no personal experience with it.
In short-- I don’t think starter kits are required, or make a whole lot of sense at a certain point. I built this one because I found myself reaching for the same tools over multiple projects. My preferred stack has changed since that time, especially for back-end projects, and I found myself choosing new tools that made this starter kit redundant.
For new front-end projects, I’d probably just go with NextJS, and layer what I need on top. For back-end, I’d choose something other than JS.
I understand Lee. When I ramp down my projects, I generally try to leave a Docker setup for future readers. But of course, you have absolutely no obligation of doing anything, your work already looks amazing, I’m mostly commiserating with OP.
Any suggestions of other projects doing similar things BTW?