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 🙏

© 2025 – Pkg Stats / Ryan Hefner

envelop-plugin-extensions

v0.1.2

Published

Set extensions via your GraphQL Context

Readme

A plugin for the envelop ecosystem that adds the ability to read, set, and clear GraphQL extensions. Works with any plugin in the Envelop ecosystem, including GraphQL Yoga v3.

Getting Started

# or yarn, or npm
pnpm add envelop-plugin-extensions

Usage

Configure useExtensions() like you would any other envelop plugin. For example, in GraphQL Yoga:

import {
  useExtensions,
  type ExtensionsContext,
} from "envelop-plugin-extensions";
import { createYoga, createSchema } from "graphql-yoga";

// Provide your schema
const yoga = createYoga({
  schema: createSchema({
    typeDefs: /* GraphQL */ `
      type Query {
        greetings: String!
      }
    `,
    resolvers: {
      Query: {
        greetings: (parent, args, context, info) => {
          // set an extension value. context.extensions is Map<string, unknown>
          context.extensions.set("extension key", "extension value");
          return "Hello World!";
        },
      },
    },
  }),
  plugins: [useExtensions(options)],
});

// Start the server and explore http://localhost:4000/graphql
const server = createServer(yoga);
server.listen(4000, () => {
  console.info("Server is running on http://localhost:4000/graphql");
});

And see the extensions property carried into the response:

{
  "data": {
    "greetings": "Hello World!"
  },
  "extensions": {
    "extension key": "extension value"
  }
}

Options

  • filter: (key: string, value: unknown) => boolean - Allows filtering extensions by top-level key. Not all extensions should be surfaced, and filter() gives you a means to run a test against every key/value before the extensions are written to the graphql response. TypeScript Users: the type for value is unknown, and it's expected if you're checking extension values you have suitable typeguards or validators.

License

MIT