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 🙏

© 2024 – Pkg Stats / Ryan Hefner

graphql-sunset

v1.0.1

Published

Sunset your GraphQL operations.

Downloads

6

Readme

graphql-sunset

Easily add support for the Sunset header to your GraphQL server to better communicate upcoming breaking changes.

Usage

  1. Add a sunset directive to your schema.

    directive @sunset(
      url: String!
      when: String!
    ) on FIELD_DEFINITION
    
    # ...

    💡 If you prefer more specific types (e.g. Instant! / URL!), then you can use them. If your GraphQL server parses these fields to something other than a string, you will need to specify a custom parseDirectiveArgs function when instantiating the plugin.

  2. Apply it to a field:

    type Query {
      greeting: String @sunset(
        url: "https://docs.your-app.com/removal-of-greeting"
        when: "2025-01-01T00:00:00.000Z"
      )
    }
  3. Add the plugin to your Apollo server.

    import { ApolloSunsetPlugin } from 'graphql-sunset';
    
    // ...
    
    const server = new ApolloServer({
      // ...
      plugins: [
        new ApolloSunsetPlugin({
          directiveName: 'sunset',
          // parseDirectiveArgs
        }),
      ],
    });
  4. Run a GraphQL operation, and see the Link and Sunset headers get populated:

    $ curl --include --request POST \
        --header 'content-type: application/json' \
        --url http://localhost:4000/ \
        --data '{"query":"query ExampleQuery {\n  greeting\n}"}'
    HTTP/1.1 200 OK
    ...
    sunset: Wed, 01 Jan 2025 00:00:00 GMT
    link: <https://docs.your-app.com/removal-of-greeting>; rel="sunset"
    ...
    
    {"data":{"greeting":"Bar"}}

Roadmap

  • [x] Output fields
  • [x] Field arguments
  • [x] Input object fields
  • [ ] Enum values