> What's the advantage of using this tool instead of apollo-cli/apollo-codegen?

> Unfortunately I'm not yet able see any benefits you'd get over Apollo's codegen in return

> Doesn’t Apollo’s Codegen tool already solve this?

I am sorry for my late response.

I add the section to README.md which explains why I created this library even there is Apollo CLI's codegen.

https://github.com/acro5piano/typed-graphqlify#why-not-use-a...

In short,

- Simplicity make this tool works as expected

- Can handle multiple schemas

- Works without schema file

I wrote a lot there, but I just wanted to try the paradigm TypeScript -> GraphQL conversion, because there are no tools to do that, unlike GraphQL -> TypeScript conversion tools.

However, this is not just a hobby project, cause I use this in my current real world project, and it reduces a lot of boilorplate. So I submit here.

# I thought Apollo codegen needs .graphql extension and webpack loader, but it reads .ts files too... Awesome.