npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fumadocs/graphql

v0.4.2

Published

Generate docs for your GraphQL schema

Readme

Fumadocs GraphQL

Generate API reference docs from GraphQL schemas for Fumadocs, with an interactive playground.

npm i @fumadocs/graphql graphql

graphql is a peer dependency.

Quick Start

Create the server instance from your schema:

// lib/graphql.ts
import { createGraphQL } from '@fumadocs/graphql/server';

export const graphql = createGraphQL({
  input: ['./schema.graphql'],
});

Add the generated pages to your source:

// lib/source.ts
import { loader } from 'fumadocs-core/source';
import { defineDocs } from 'fumadocs-mdx/macro';
import { graphql } from './graphql';

const docs = defineDocs({
  dir: 'content/docs',
});

export const source = loader(
  {
    docs: docs.toFumadocsSource(),
    graphql: await graphql.staticSource({
      // a route group, generated pages won't have a `/graphql` prefix in their URLs
      baseDir: '(graphql)',
      meta: true,
    }),
  },
  {
    baseUrl: '/docs',
    plugins: [graphql.loaderPlugin()],
  },
);

Render them from a client component:

// components/api-page.tsx
'use client';
import { createGraphQLPage } from '@fumadocs/graphql/ui';

export const GraphQLPage = createGraphQLPage({
  playground: {
    url: '/api/graphql',
  },
});
// app/docs/[[...slug]]/page.tsx
if (page.type === 'graphql') {
  return (
    <DocsPage toc={page.data.toc} full>
      <DocsTitle>{page.data.title}</DocsTitle>
      <DocsDescription>{page.data.description}</DocsDescription>
      <DocsBody>
        <GraphQLPage {...page.data.getGraphQLPageProps()} />
      </DocsBody>
    </DocsPage>
  );
}

And import the styles in your global CSS:

@import '@fumadocs/graphql/css/preset.css';

Options

Inputs

input accepts an array of file paths/URLs to SDL files, or a record of schema id to input:

  • SDL file paths/URLs, or SDL text (including extend type definitions).
  • Introspection results (JSON).
  • GraphQLSchema instances.

Page Presets

Pass options to staticSource() to control the generated pages:

  • per: 'item' (default): a page per operation/named type, use groupBy ('kind' | 'none' or a function) to group them into folders, and includeOperations/includeTypes to filter items.
  • per: 'file': a single page per schema.
  • per: 'custom': bring your own pages builder.

UI

createGraphQLPage() accepts:

  • Cross-links of type & operation references are pre-generated when you pass baseUrl (the baseUrl of your loader()) to staticSource(); override them with the typeLinks/operationLinks callbacks if needed.
  • playground: interactive playground shown on operation pages — url (GraphQL endpoint, operations are sent over HTTP POST), fetcher (replace the default fetcher, e.g. to proxy requests), or render (replace the playground UI).
  • shikiOptions, components, and content/schemaUI render slots for deeper customisation.

See Fumadocs docs for more.