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

piggyback.js

v0.0.1

Published

Reuse function results for multiple callers

Downloads

3

Readme

Build Status

piggyback.js

Sometimes you have a function, and sometimes that function takes a while to execute. Sometimes other functions invoke that function while it's already executing, making it execute again and again. Maybe that even happens a few more times. But in this arbitrary example, all of those functions that called the original function (the one that takes a while), they just want the same thing.

What if we just used the result from the first invocation for everything?

Huh? (The Problem)

You need to make a call. A call to an API somewhere. So you make a function, myRequest, to handle that API call. Let's say you've even added a caching mechanism since that call may take seconds to complete -- the next time you make the same call it'll finish a lot faster.

Warning: pseudo-code below, hopefully it's clear enough

function myRequest(params) {
  let key = `myRequest:${hashMyParams(params)}`

  return cache.get(key).then((cached) => {
    if (cached) {
      return cached
    }

    return apiClient.get(params.url).then((res) => {
      return cache.set(key, res)
    })
  })
}

That's great! It'll store the result for next time. I'm feeling good. But suddenly...

// this happens somewhere
myRequest({
  url: '/a-fun-url-with-fun-data'
}).then(...)

// immediately afterwards, this happens somewhere else
myRequest({
  url: '/a-fun-url-with-fun-data'
}).then(...)

That's the same request. Twice. Maybe even thrice. And they're happening in such short succession that there's no chance to cache the result from the first invocation and use it for the second. Hrmph. We end up hitting the API multiple times and waiting forever for both responses. So now what?

Cool! (The Solution)

Let's update myRequest with piggyback.js.

import piggyback from 'piggyback.js'

function myRequest(params) {
  let key = `myRequest:${hashMyParams(params)}`

  return piggyback(key, () => {
    return cache.get(key).then((cached) => {
      if (cached) {
        return cached
      }

      return apiClient.get(params.url).then((res) => {
        return cache.set(key, res)
      })
    })
  })
}

Now any duplicate request that happens in quick succession of the original will "piggyback" on the original request's result, the API call and caching only happens once.

License

The MIT License (MIT)

Copyright (c) 2015 Code & Craft, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.