Bundlephobia requires the entrypoint field in package.json. In the next patch release this will be added

Given the goal of this project is to act as mostly-full replacement for apollo client in javascript projects, it seems only fair that jraph supports GraphQL Subscriptions as well. This task will not only require some research on my part, but a lot of work into making sure that users aren’t forced to import something with a feature that’s useless to them. So code-splitting must be designed and implemented properly as well. I am also toying with the notion of supporting graphql server creation. Though I think that is outside the scope of this project.

I have an issue with this appearing to be an Apollo wannabe

In the future, I am going remove isomorphic fetch as a dependency, and just include node-fetch if(!global.fetch) or if(!window)

So, I've created two versions of jraph. The version in master is the version available on NPM now. The other version, is under the gql branch. You can look at either to view the syntax difference, if you'd like. I need your help to decide what version stays and what version goes, or for another solution. My solution so far is to publish a nice and polished version with the current syntax, and then publish a new major version with the new syntax.