What is the reason to make one adapter for all runtimes instead N adapters for N runtimes?

[krutoo]

Hi, first of all thanks for creating this library.

In my case i want to create server based on Fetch API from node js because such runtimes as Bun and Deno already implements Fetch API based servers

I need to adapter exactly for Node.js and i notices that @whatwg-node/server takes ability to create adapter for each runtime

What is the reason to make one adapter for all runtimes instead N adapters for N runtimes?

[ardatan]

• Simplicity of maintenance and usage, easier to maintain one abstraction instead of multiple variants...
• Easy to test; adapter.fetch simulates the request just like regular Fetch.

As a library maintainer, you don't have to worry about testing all the environments and focus on your impl based on Fetch API. You can see our tests in feTS and GraphQL Yoga as an example.

If you want to have N adapters for N runtimes, you can use @whatwg-node/server just for Node.js. It is up to you.