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

graphql-cached

v0.1.6

Published

Write a cache layer for each resolver in GraphQL Shield style with Memcached

Downloads

24

Readme

⚡️ GraphQL Cached

Write a cache layer for each resolver in GraphQL Shield style with Memcached

Dependencies

Install

$ yarn add graphql-cached

Usage

with graphql-tools

import { cached } from 'graphql-cached'
import { applyMiddleware } from 'graphql-middleware'
import Memcached from 'memcached'
import schema from './schema'

const memcached = new Memcached('my.memcached.host:11211')

// Generated resolver types by `@graphql-codegen/cli`
import { Resolvers } from './__generated__/resolvers'
import { Context } from './context'

const middleware = cached<Context, Resolvers>(
  {
    User: {
      image: {
        key(parent, args, context) {
          // it's type-safe!
          return parent.imageId
        },
        lifetime: 5,
        serializer: {
          serialize(item) {
            return item
          },
          deserialize(serializedItem) {
            return new Image(serializedItem)
          },
        },
      },
    },
  },
  {
    memcached,
    contextKey(context) {
      return 'v1.' + context.user?.role || 'Anonymous'
    },
  }
)

// Now schema is automatically cached!
const cachedSchema = applyMiddleware(schema, middleware)

Cache Field

Required

  • key: fieldKey generation function

Optional

  • lifetime: How much time to keep the cache (seconds) (default: 10 seconds)
  • serializer: Preprocess item before storing in cache and after fetching from cache

Configuration

Required

  • memcached: Memcached client instance
  • contextKey: Key generation function based on Context

Life cycle hooks (Optional)

  • beforeGet: Triggered before cache fetching
  • afterGet: Triggered after cache fetching
  • beforeSave: Triggered before cache storing
  • afterSave: Triggered before cache storing
  • onHit: Triggered when cache hit
  • onMiss: Triggered when cache miss

Full cache key

{contextKey}${typeName}${fieldName}${fieldKey}

Examples

v1.Admin$User$image$dbf66e27-9bb4-5682-b890-ecf34fe63333

v1.User$Query$user${"where":{"id":"57c5fb3f-a5e7-5b4f-a7ed-ab50281b8222"}}

⚠️ Be careful!

If there are resolvers with different responses for different users, carefully write the key generation function. Items cached for one user may be visible to other users.

Also, if there is a cached item, the existing resolver does not work. If you want to do permission-related logic before cache layer, I recommend using it with graphql-shield.

const schemaWithMiddleware = applyMiddleware(
  schema,
  authMiddleware, // created with graphql-shield
  cachedMiddleware // created with graphql-cached
)

For more information on how GraphQL Middleware works, check out GraphQL Middleware.

Usage examples

If you have a feature request or a bug, please create a new issue. And also, pull requests are always welcome🙏