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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-yoga/common	2.7.0 -> 2.12.7

---

Release Notes

dotansimha/graphql-yoga

v2.12.7

Compare Source

Patch Changes

• #​1634 5193e43 Thanks @​n1ru4l! - Use 'correct' deep import for working around unpkg limitations of not supporting the package.json exports map.

v2.12.6

Compare Source

Patch Changes

• #​1603 e4e8ade Thanks @​n1ru4l! - Update @envelop/core which resolves swallowed context errors with error masking.

• #​1600 94b41f3 Thanks @​n1ru4l! - Apply the HTTP validation error plugin last in order to not interfere error masking when using the handleValidationErrors option.

v2.12.5

Compare Source

Patch Changes

• eecf24c: Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext
• Updated dependencies [eecf24c]
  • @​graphql-yoga/subscription@​2.2.3

v2.12.4

Compare Source

Patch Changes

• c00dad3: Resolve issue where @whatwg-node/fetch caused other fetch to fail processing HTTP requests.

v2.12.3

Compare Source

Patch Changes

• 889d16d: Now GraphQL Yoga throws a better descriptive error message if the client sends a request with a non-string query parameter instead of expecting graphql.parse to fail and throw a cryptic JS TypeError.

v2.12.2

Compare Source

Patch Changes

• 3363de2: Use import type { Foo } from '@​pkg' instead of import { type Foo } from '@​pkg' as many tools don't yet support this syntax.
• Updated dependencies [3363de2]
  • @​graphql-yoga/subscription@​2.2.2

v2.12.1

Compare Source

Patch Changes

• Updated dependencies [ebddc71]
  • @​graphql-yoga/subscription@​2.2.1

v2.11.0

Compare Source

Minor Changes

• 5bcd8ea: Improve DX for Cloudflare Workers and other environments like Bun that needs a default export with a fetch method

  • You no longer need to export fetch specifically in a different object. Instead, you can export Yoga instance directly.

  Before in CF Workers Modules you had to do;

  import { createServer } from '@​graphql-yoga/common'
  
  const server = createServer()
  
  export default {
    fetch: server.fetch,
  }

  Now you can export Yoga instance as-is like below;

  import { createServer } from '@​graphql-yoga/common'
  
  export default createServer()

  • Environment object is now passed as ServerContext to the execution. So you can access KV Namespaces and other Env variables in the context.

  import { createServer } from '@​graphql-yoga/common'
  
  interface Env {
    MY_NAMESPACE: KVNamespace
    SOME_TOKEN: String // An example environment variable
  }
  
  export default createServer<Env>({
    typeDefs: /* GraphQL */ `
      type Query {
        todo(id: ID!): String
        todos: [String]
      }
      type Mutation {
        createTodo(id: ID!, text: String!): String
        deleteTodo(id: ID!): String
      }
    `,
    resolvers: {
      Query: {
        todo: (_, { id }, { MY_NAMESPACE }) => MY_NAMESPACE.get(id),
        todos: (_, __, { MY_NAMESPACE }) => MY_NAMESPACE.list(),
      },
      Mutation: {
        // MY_NAMESPACE is available as a GraphQL context
        createTodo(_, { id, text }, context) {
          return context.MY_NAMESPACE.put(id, text)
        },
        deleteTodo(_, { id }, context) {
          return context.MY_NAMESPACE.delete(id)
        },
      },
    },
  })

v2.10.0

Compare Source

Minor Changes

• 8947657: ## Correct status code for multipart request errors

  Return correct 413 (Request Entity Too Large) HTTP status code if the given request body is larger then the specified one in multipart options.
  Previously it was returning 400 or 500 which is an incorrect behavior misleading the client.

v2.9.0

Compare Source

Minor Changes

• 7de07cd: Support TypeScript ECMA script resolution. More information on https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#ecmascript-module-support-in-node-js

Patch Changes

• 8922c3b: ## Multiple parameters are not recommended (not used internally) for log methods

  Previously sometimes Yoga used to send data to the provided logger like below;

  yogaLogger.debug(arg1, arg2, arg3)

  This behavior is working fine with JavaScript's native console implementation but most of the other non native logger implementation like Pino only accept a single parameter for its logging methods. So we decided to avoid sending multiple parameters to the logger.
  However, in order to prevent a breaking change, we kept the signatures of logger methods and they will still accept multiple parameters in a single call. You should keep on mind that eventually we will stop accepting multiple parameters and have the behavior similar to Pino's.

v2.8.3

Compare Source

Patch Changes

• 2c0bcda: Remove 'Server: GraphQL Yoga' header from the response

v2.8.2

Compare Source

Patch Changes

• a06091f: '.inject' should set Content-Type to application/json by default. Previously the user should have set it.

v2.8.1

Compare Source

Patch Changes

• 06652c7: Fix GraphQLYogaError being thrown from contextFactory to be treated as an unexpected error. The bug would previously prevent the GraphQLYogaError extensions from being exposed in the result and cause a status code of 500.
• a4960bd: Ensure the GraphiQL version is compatible with the @graphql-yoga/common version by hard-coding the version number before publishing/building.

v2.8.0

Compare Source

Minor Changes

• c96e7c2: Support application/graphql, application/x-www-form-urlencoded and application/graphql+json as defined in GraphQL over HTTP specification and implemented in express-graphql reference implementation so Yoga now accepts the following request bodies with specific "Content-Type" headers;

  • application/graphql can accept query something { somefield } which takes the GraphQL operation directly as POST request body
  • application/x-www-form-urlencoded can accept query=something&variables={"somefield": "somevalue"} which takes the GraphQL operation and variables as POST request body

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 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 Mend Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for redwoodjs-docs canceled.

Name	Link
🔨 Latest commit	b8ac62d
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodjs-docs/deploys/63033229413f880008cc74fd

[dthyresson]

@Tobbe Does #6241 setting the content type when pre-rendering fix this build issue?

[Tobbe]

@dthyresson That's what I'm hoping

[pchc2005]

Hi, may i know what is the plan of v2.2.1 release?

[Tobbe]

@pchc2005 Yes, we're aiming for a patch release as soon as possible

[Tobbe]

@pchc2005 Patch release out: https://github.com/redwoodjs/redwood/releases/tag/v2.2.1

[pchc2005]

Great thanks @Tobbe !