Unknown directive \"@defer\ and @stream

[koo27]

Describe the bug

I'm trying to use the two directives @defer and @stream with no luck.
I set up a simple grapqhl yoga server, but the response I get from graphiQL is always "Unknown directive".
Here is a response example

{
  "data": null,
  "errors": [
    {
      "message": "Unknown directive \"@defer\".",
      "locations": [
        {
          "line": 5,
          "column": 17
        }
      ],
      "extensions": {}
    },
    {
      "message": "Unknown directive \"@stream\".",
      "locations": [
        {
          "line": 8,
          "column": 13
        }
      ],
      "extensions": {}
    }
  ]
}

I also created a public report just for this test to let you try it out. This is the repo: https://github.com/koo27/defer-stream-test
I set up a urql client too, but I get the same response anyway.

What am I doing wrong?

Your Example Website or App

https://github.com/koo27/defer-stream-test

Steps to Reproduce the Bug or Issue

1. Go to the test repo I linked
2. clone it, install dependencies and start the server
3. run a query with defer or stream

Expected behavior

I expect @defer and @stream to work

Screenshots or Videos

No response

Platform

• OS: [macOS]
• NodeJS: [e.g. 18.2.0]
• "@graphql-yoga/node": "^2.12.0",
• "graphql": "^16.5.0"

Additional context

No response

[saihaj]

Hey! @koo27 to use defer and stream you need to use experimental release from graphql-js https://github.com/graphql/graphql-js/releases/tag/v16.1.0-experimental-stream-defer.6 for new major release of graphql-yoga we plan to provide out of box support #1352

[koo27]

Thank you for your reply. I did actually update graphql version in my package.json, but I got the same error. You can check the same repo I created

[saihaj]

Using defer and stream is an opt-in checkout the experimental branch docs: https://deploy-preview-3659--compassionate-pike-271cb3.netlify.app/docs/tutorials/defer-stream
Here is the reference implementation PR and it can link you to all the discussion for this opt-in change: graphql/graphql-js#3659