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

@northernv/dataloader

v1.2.0

Published

A framework for dataloaders in models

Downloads

7

Readme

@northernv/dataloader

npm MIT licensed

Usage

npm install -S @northernv/dataloader;
yarn add @northernv/dataloader;

In your models, that are Javascript classes, include a static function called loaders that returns an object of dataloaders

class Property {
  static loaders (DataLoader, { db }) {
    const manyPropertyById = new DataLoader(propertyIds => {
      return db('property').whereIn('id', propertyIds)
        .then(rows => propertyIds.map(id => rows.filter(x => x.id === id)))
    })

    const manyPropertyByAssociationId = new DataLoader(associationIds => {
      return db('property').whereIn('property.assocation_id', associationIds)
        .then(rows => associationIds.map(id => rows.filter(x => x.assocationId === id)))
    })

    const onePropertyById = new DataLoader(propertyIds => {
      return db('property').whereIn('id', propertyIds)
        .then(rows => propertyIds.map(id => rows.find(x => x.id === id)))
    })
    return { manyPropertyById, manyPropertyByAssociationId, onePropertyById }
  }
}

Each loader should follow the patter one<ClassName>By<PropertyName> or many<ClassName>By<PropertyName>

In your bootstrapping file

const loader = dataloaders('models', { db })

const server = new ApolloServer({
  schema,
  // Create new Dataloaders for each request
  context: ({ req, res }) => new Context({ req, res, db, channel, loaders: loader() }),
  formatError: (error) => {
    Sentry.captureException(error)
    return { ...error, code: get(error, 'originalError.constructor.name', 'Unknown') }
  },
})

or you can delay adding the db option until runtime

// Notice here we do not pass in the run time option `db`
const loader = dataloaders('models')

const server = new ApolloServer({
  schema,
  // Create new Dataloaders for each request
  // Instead we pass in the runtime option `db` here on init
  context: ({ req, res }) => new Context({ req, res, db, channel, loaders: loader({ db }) }),
  formatError: (error) => {
    Sentry.captureException(error)
    return { ...error, code: get(error, 'originalError.constructor.name', 'Unknown') }
  },
})

See how we pass in the model directory that is relative to the project root and our options. The options will be passed to each of the loaders functions

Notes

  • It will throw an error if there are two loaders with the same name, so sticking to the naming convention is important.
  • Many loaders use filter, while One loaders user find
  • It assumes that items are loaded from a database