apollo-server VS Hoppscotch

Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and I’m curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.

There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.

As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.

[1] https://github.com/apollographql/apollo-server/blob/9817bc47...

While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, we’ve got a strong indication we took the right approach.

GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.

After some head-scratching, I opened an issue on Apollo Server’s GitHub repository. There, Apollo Server contributor @​glasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Server’s context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:

Apollo as a middleware in Express.js, actually.

Apollo Server 3 Cookie Issue #5775

Lastly, instead of writing our API core ourselves, we'll be using the star of this episode --- Apollo Server (a.k.a. GraphQL server). It has detailed documentation available here.

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 🤝 .