For each release of GraphQL.js, we are now publishing an accompanying release containing an experimental implementation of the @defer and @stream directives. We are hoping to get community feedback on these releases before the proposal is accepted into the GraphQL specification.

You can use this experimental release of GraphQL.js by adding the following to your project's package.json file.

"graphql": "experimental-stream-defer"

A similar release of express-graphql will be coming soon.

I am creating this issue as a placeholder for anyone who has tried out these experimental packages to leave feedback. Please let us know if everything is working as expected or if you run into any issues. Any suggestions for improvements are also welcome.

References:

• Demo repo
• Conference talk about defer/stream
• defer/stream RFC
• Spec edits
• graphql-js branch
• express-graphql PR
• graphql-over-http RFC
• fetch-multipart-graphql (client library)
• meros (client library)

Feedback received so far

Call return on iterable when connection closes

• Raised by @danielrearden
• graphql-js
  • Fixed: Return underlying AsyncIterators when execute result is returned #2843
  • Released: TBD
• express-graphql
  • Fixed: graphql/express-graphql@ce8429e
  • Released: express-graphql@0.12.0-experimental-stream-defer.1

content-length in payload should not be required, parsers should use boundary instead

• Raised by @maraisr
• graphql-over-http spec
  • Fixed: Spec edits for multipart @defer @stream around content-length graphql-over-http#152
• fetch-multipart-graphql
  • Fix: WIP
• express-graphql
  • Fix: feat: remove the need for content-length robrichard/express-graphql#1