express-graphql VS Postwoman

It looked a little janky but it actually worked fine. But then I needed file uploads. Something graphql-zeus does not support. So I had to create a small wrapper for the SDK created so that it worked. And then also express-graphql, the server I was using, was deprecated.

This seems like a minor deal unless you're not using Express as your web framework. And an important note here is that Express GraphQL is being deprecated by the GraphQL Foundation. So if you're using Express for a GraphQL API, you should move away from it anyway.

You might have seen other GraphQL server solutions where the schema is implemented by using a more programmatic approach. Here is an example of how schemas are implemented using the express-graphql library. (link: https://github.com/graphql/express-graphql)

I'm not sure where the "8MB limit" comes from but, indeed, there are issues like this where, in some implementations, the response size is limited to 100KB: https://github.com/graphql/express-graphql/issues/346

With Node I used express-graphql as opposed to something like Apollo because it's lighter and less heavy on resources compared to Apollo.

Daniel Rearden listed the following reasons pushing him to create Helix, believing that these factors were absent from popular solutions like Apollo Server, express-graphql and Mercurius:

Express GraphQL is a library for building production ready GraphQL HTTP middleware. Despite the emphasis on Express in the repo name, you can create a GraphQL HTTP server with any HTTP web framework that supports connect styled middleware. This includes Connect itself, Express and Restify.

If you are using Node.js there are a lot of implementations of GraphQL servers with a few being express-graphql, apollo-server, mercurius, graphql-helix and more. And if you are using other languages, you can see a great list here

express-graphql GitHub Repository

Not sure about other libraries but it's certainly not the case for express-graphql on node.js. You can tie the graphql endpoint to any method you like. On the site I work on, we have a graphql endpoint that only accepts GET requests in production and is thus cacheable by Cloudfront. In dev and staging we accept all requests so that GraphIQL works.

How can Hoppscotch help you intercept the API calls? 👽

We need you help to constantly improve Hoppscotch so that we can make it easier for you to build better software! Write to us at [email protected] or head over to our GitHub repository if you have any feedback about Hoppscotch 💚!

For the past five years, Hoppscotch 🛸 has been quietly transforming the way developers tackle their work in the API development world. Our mission has always been to make developer's lives easier and their workflows smoother, all from the comfort of their browser. And guess what? We might have evolved and gotten strong, but we are staying true to our goal of simplifying things for developers everywhere. Today, we're here to spill the beans on the simple yet powerful productivity hacks that Hoppscotch offers. Get ready to level up your development game in ways you never imagined.

Hoppscotch is a powerful yet simple-to-use API testing suite. It removes a lot of complexity, making it easy for anyone to get started with API testing. Try Hoppscotch now!

Hoppscotch - HTTP client used for sending notifications through the Google API.

We began as a web-based API client at hoppscotch.io, where anyone can easily initiate API testing. Ever since then the Hoppscotch Desktop app has been a highly requested product by our community. We've been listening and are excited to announce that the day has finally arrived - today marks the launch of the public alpha version of the Hoppscotch Desktop App for macOS, Windows, and Linux!

We’re building an open-source Postman alternative.

1.6m+ users, 100k+ monthly active users, 55k+ GitHub stars.

Web app: https://hoppscotch.io

The collective efforts and commitment of our team has led Hoppscotch towards remarkable improvements on its path to transforming the API development ecosystem. But, the speed of evolution we've experienced wouldn't have been possible without the open-source nature of Hoppscotch. A significant portion of our success is attributed to our dedicated contributors who have resolved existing issues, filed bug reports, authored blogs, created tutorials, and spread the word about Hoppscotch within their networks 🤝 .