graphql-yoga 5.x

Use graphql-yoga ^5.0.0 to build a Fetch-compatible GraphQL handler, execute it directly in scripts, and configure documented readiness and error-handling plugins. Avoid legacy Yoga v2/v4 server shapes.

For

graphql-yoga@5.22.0

Verified

2026-09-07, 3 examples executed

Package

@modootoday/pmcp-graphql-yoga@5.0.0

What it covers

• Current API shape
• Running Yoga with Node HTTP
• Readiness checks
• Error coordinates and masking
• v5 migration traps
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict'
import { createSchema, createYoga } from 'graphql-yoga'

const schema = createSchema({
  typeDefs: /* GraphQL */ `
    type Query {
      hello: String
    }
  `,
  resolvers: {
    Query: {
      hello: () => 'world'
    }
  }
})

const yoga = createYoga({ schema })

const response = await yoga.fetch('http://yoga/graphql', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ query: '{ hello }' })
})

assert.equal(response.status, 200)
assert.deepEqual(await response.json(), {
  data: { hello: 'world' }
})

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-graphql-yoga

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.