You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-6Lines changed: 15 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,9 @@ Minimal GraphQL client supporting Node and browsers for scripts or simple apps.
25
25
-[Why do I have to install `graphql`?](#why-do-i-have-to-install-graphql)
26
26
-[Do I need to wrap my GraphQL documents inside the `gql` template exported by `graphql-request`?](#do-i-need-to-wrap-my-graphql-documents-inside-the-gql-template-exported-by-graphql-request)
27
27
-[What sets `graphql-request` apart from other clients like Apollo, Relay, etc.?](#what-sets-graphql-request-apart-from-other-clients-like-apollo-relay-etc)
28
+
-[Project Stats](#project-stats)
29
+
-[Package Installs](#package-installs)
30
+
-[Repo Beats](#repo-beats)
28
31
29
32
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
We only (officially) support [versions of Nodejs](https://github.com/nodejs/Release#release-schedule) of the following status:
@@ -203,3 +200,15 @@ No. It is there for convenience so that you can get the tooling support like aut
203
200
`graphql-request` is the most minimal and simplest to use GraphQL client. It's perfect for small scripts or simple apps.
204
201
205
202
Compared to GraphQL clients like Apollo or Relay, `graphql-request` doesn't have a built-in cache and has no integrations for frontend frameworks. The goal is to keep the package and API as minimal as possible.
0 commit comments