fix(deps): update dependency @graphql-yoga/common to v2.2.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-yoga/common	2.0.0 -> 2.2.1

---

Release Notes

dotansimha/graphql-yoga

v2.2.1

Compare Source

Patch Changes

• 32e2e40: Thanks to the recent release of DataLoader, we don't need to setImmediate for browser environments anymore.
• 32e2e40: Bump fixed cross-undici-fetch version

v2.2.0

Compare Source

Minor Changes

• 1d4fe42: new option fetchAPI has been added;

  User can provide a custom Fetch implementation to Yoga like below;

  import { fetch, Request, Response, ReadableStream } from 'my-ponyfill'
  createServer({
    fetchAPI: {
      fetch,
      Request,
      Response,
      ReadableStream,
    },
  })

Patch Changes

• 1d4fe42: Avoid extra usages of URL constructor which has some performance implications on Node

v2.1.0

Compare Source

Minor Changes

• 4077773: Allow to pass in graphiql: true or graphiql: () => true as an option to create server.

  This change makes it easier to please the TypeScript compiler for setups that disable YogaGraphiQL conditionally (e.g.g based on environment variables).

  Previously you had to write:

  createServer({
    graphiql: process.env.NODE_ENV === "development" ? {} : false
    // OR
    graphiql: process.env.NODE_ENV === "development" ? undefined : false
  });

  Now you can write the following:

  createServer({
    graphiql: process.env.NODE_ENV === 'development',
  })

• f6bcbd1: Load GraphiQL from CDN in order to reduce bundle size.

  If you need to use GraphiQL in an offline environment please follow the instructions in the docs for installing @graphql-yoga/render-graphiql.

  https://www.graphql-yoga.com/docs/features/graphiql#offline-usage

• 2739db2: Update to latest GraphiQL 1.8.4

Patch Changes

• b459c9c: Generate correct multipart response.

• e207079: Checks if the request url matches with the given endpoint and gives 404 if not.

• 86edaa3: handle cors headers correctly in case of an explicit definition of the allowed origins;

  • If request origin doesn't match with the provided allowed origins, allowed origin header returns null which will cause the client fail.
  • If request origin matches with the provided allowed origins, allowed origin header returns the request origin as it is.
  • • Previously it used to return all origins at once then the client was failing no matter what.
  • If no request origin is provided by the request, allowed origin header returns '*'.
  • • If credentials aren't explicitly allowed and request origin is missing in the headers, credentials header returns 'false' because '*' and credentials aren't allowed per spec.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for redwoodjs-docs canceled.

Name	Link
🔨 Latest commit	fc88dff
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodjs-docs/deploys/6256f7e81335640009a99c46