Move logic from apollo-server-cloudflare to this repo with Apollo Server 4?

[glasser]

Hi! We're starting our work on Apollo Server 4. You can see details in our full roadmap but the overview is that instead of shipping Apollo Server with 9 core-maintained integrations with web frameworks and serverless environments (but providing no means for adding more integrations), we will provide a stable API for anyone to provide an integration with their favorite web environment (essentially an abstract representation of HTTP requests and responses). We will continue to actively maintain HTTP handlers that work with Node's built-in http objects (including an Express-style middleware) but we will be shifting integrations with other web environments to community-maintained.

One of those 9 currently-core-maintained integrations is apollo-server-cloudflare, which is used by this project. It consists of a small amount of code that registers a fetch event listener and converts between fetch-style requests and the type that Apollo Server 3 understands. As you may have noticed, this hasn't been particularly actively maintained since its creation over three years ago, and it's one of the integrations that we will be transitioning to community maintenance.

We've opened an issue on our repo looking for folks interested in maintaining the AS4 version of this package. That said, as far as we know the only reason people end up using apollo-server-cloudlfare is because they're using this quickstart. So one possibility might be that we can get rid of apollo-server-cloudflare entirely and write the glue code directly in this repository. (Note that one of the goals for AS4 is that the glue code should end up a lot simpler than the existing glue code, which itself is under a hundred lines of code.)

Does that make sense as an alternative?