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

@btravstack/graphql-server

v0.48.0

Published

The GraphQL Yoga answerer for @btravstack/http-server

Readme

@btravstack/graphql-server

A GraphQL Yoga answerer for the protocol-neutral @btravstack/http-server runtime. Supply any GraphQLSchema; the package has required GraphQL and Yoga peers and no oRPC server dependency. graphql(defineAuth(), { schema }) contributes a HttpHandler member. A request-scoped unit and the Node incoming request are available to resolvers. Use GraphqlModule for a deployment root:

import { GraphqlModule, graphql } from "@btravstack/graphql-server";
import { defineAuth } from "@btravstack/http-server";
import { createSchema } from "graphql-yoga";

const schema = createSchema({
  typeDefs: "type Query { hello: String! }",
  resolvers: { Query: { hello: () => "world" } },
});

export const GatewayApi = GraphqlModule("GatewayApi")({
  answerer: graphql(defineAuth(), { schema }),
});

The module composes the listener, authenticators and declared request modules. It exports the runtime ports and available Logger / HealthChecks without exposing business ports automatically. Its socket options are the HTTP runtime's, excluding cors and compression. Set CORS on graphql(); the answerer does not apply HTTP compression. Schema, authentication and Yoga options stay on graphql().

Pass units with unit to check each injected port against the module the selected request kind actually forks. GraphqlModule binds that record to the runtime automatically. Yoga plugins and CORS policy are explicit options; the wildcard CORS default and Yoga console logging are disabled, and a masked defect is reported to Observers instead. GraphiQL, introspection and "Did you mean …" suggestions stay off unless GRAPHQL_DEVELOPER_TOOLS=true (or developerTools: true) turns them on. A document over GRAPHQL_MAX_TOKENS (default 1000, pinned by maxTokens) is refused by the parser, before validation. fieldResult(result) answers a resolver from an AsyncResult, with a refusal on its own field's path. Preflights use Yoga's CORS policy before authentication, and Yoga plugins are disposed when the application stops.

See Serve GraphQL and the separate GraphQL gateway.