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
All changes not currently in 16.x.x were extracted into #4551
This PR aligns next and v17-alpha (which is next rebased on 16.x.x), so
after we switch to v17-alpha (the next version of next), proper
attribution and history of all changes will be preserved. This commit
just allows us to prove more decisively that next and v17-alpha are
content equivalent.
Copy file name to clipboardExpand all lines: website/pages/docs/running-an-express-graphql-server.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ The simplest way to run a GraphQL API server is to use [Express](https://express
13
13
npm install express graphql-http graphql --save
14
14
```
15
15
16
-
Let's modify our “hello world” example so that it's an API server rather than a script that runs a single query. We can use the 'express' module to run a web server, and instead of executing a query directly with the `graphql` function, we can use the `graphql-http` library to mount a GraphQL API server on the “/graphql” HTTP endpoint:
16
+
Let's modify our "hello world" example so that it's an API server rather than a script that runs a single query. We can use the 'express' module to run a webserver, and instead of executing a query directly with the `graphql` function, we can use the `graphql-http` library to mount a GraphQL API server on the "/graphql" HTTP endpoint:
0 commit comments