Interesting, I will agree that configuring an express server and GQL resolvers has a similar structure, in that they're composed of "routes" and "handlers" ("ty

Interesting, I will agree that configuring an express server and GQL resolvers has a similar structure, in that they're composed of "routes" and "handlers" ("types" and "resolvers"). The biggest potential use case here would be to allow the server to expose a REST-style API as well as a GraphQL one with the same codebase - is that supported by this package? IMO it definitely should be. The only other reason I can think of to use this is if you are used to writing express servers and don't want to change, which isn't a very good reason to use yet another package. graphql-tools makes writing the server pretty dead easy.