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

connected-dataloader

v1.0.0

Published

Create data loaders connected to a common backing storage.

Downloads

3

Readme

connected-dataloader

This package allows you to create DataLoader instances which share a common cache storage. Loads performed with one DataLoader will automatically prime the cache of other DataLoader instances that are linked to the same storage.

This is useful in cases where a particular piece of data can be located through multiple loaders—for example, a user might be loadable by either their ID or email address.

The connected DataLoader abstraction frees up developers from manually managing cache entries, and decouples DataLoaders from the technical details of each other's cache key function.

Before:

const byId = new DataLoader<string[], User>(async (keys) => {
  const users = await db.users.findMany({
    where: { id: { in: keys } },
  });

  // This is duplicated
  for (const user of users) {
    byEmail.clear(user.email).prime(user.email, user);
  }

  return users;
});

const byEmail = new DataLoader<string[], User>(async (keys) => {
  const users = await db.users.findMany({
    where: { email: { in: keys } },
  });

  // And also means `byEmail` is coupled to cache key semantics of `byId`
  //   (and vice versa!)
  for (const user of users) {
    byId.clear(user.id).prime(user.id, user);
  }

  return users;
});

After:

import {
  ConnectedLoader,
  ConnectedLoaderStorage,
} from 'connected-dataloader';

// Shared storage for connected loaders
const storage = new ConnectedLoaderStorage<string, User>();

// This loader will automatically prime `byEmail`'s cache
const byId = new ConnectedLoader(
  async keys =>
    db.user.findMany({
      where: { id: { in: keys } },
    }),
  // `valueKey` defines mapping from `user` object => cache key
  { storage, valueKey: user => user.id },
);

const byEmail = new ConnectedLoader(
  async keys =>
    db.user.findMany({
      where: { id: { in: keys } },
    }),
  { storage, valueKey: user => user.email },
)