Migrate away from express-graphql package #1420
Labels
Comments
13 tasks
|
+1 for Apollo Server |
timheilman
added a commit
to timheilman/cypress-realworld-app
that referenced
this issue
Mar 5, 2024
…nd-middleware-express toward resolution of issue cypress-io#1420 and cypress-io#1508
cacieprins
added a commit
that referenced
this issue
May 20, 2024
#1521) * build: replace express-graphql with graphql-http and graphql-playground-middleware-express toward resolution of issue #1420 and #1508 * fix: go ahead and preempt provision of GET at /graphql by graphql-http with graphql-playground-middleware-express, rather than serving it from GET /gql-playground. This preserves functionality closer to as it was with express-graphql. * fix: whoops did not mean to modify database.json * Update backend/app.ts Co-authored-by: Cacie Prins <cacieprins@users.noreply.github.com> * style: do not pollute type system with one-off inline types * fix: consume rename commited on github from reviewer suggestion * style: do not pollute Query.ts either with one-off inline types * build: empty commit to clear perhaps spurious circleCI failure on firefox all specs passing on firefox locally. --------- Co-authored-by: Cacie Prins <cacieprins@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
express-graphqlpackage is deprecated and does not support the version of GraphQL that we're on. We should move off of it to a different GraphQL server package that still allows us to easily standup GraphiQL. Possible candidatesThe text was updated successfully, but these errors were encountered: