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

request-once

v1.0.3

Published

Collects multiple requests to the same URL into one Promise

Downloads

2

Readme

Request Once

One Request to rule them all, One Request to find them. One Request to bring them all, and in the darkness bind them.

Maintains a keyed pool of pending asynchronous requests and returns a promise to be fulfilled when that request finishes. Essentially it allows you to save resources if you have a bunch of unrelated codepaths attempting to access the same resource at once. An example use case is an application that spawns many concurrent network requests which may be accessing the same url. request-once allows you to optimize this without thinking about batching things so as to avoid opening additional sockets unnecessarily.

Usage

Install it:

npm install --save request-once

Use it:

// options (optional) recognizes:
//
// {
//   clone: Boolean (default false),
//   freeze: Boolean (default false)
// }
//
// clone returns a deep copy of the result to any
// chained promises so they can manipulate them
// individually
//
// freeze recursively freezes the result, so if
// the same object is passed to multiple request
// handlers, they aren't able to step on each other's
// toes

var fn = function(url) {
  return request_promise.get(url)
}

var options = { freeze: true }

var request = require('request-once')(fn, options)

request('https://github.com').then(function (res) {
  // do something
})

If you were then to make a request to the same url before the previous request has completed, the API will return a reference to the original request's Promise (bluebird) instead of requesting again

// won't make another request to github if first request
// is still pending

request('https://github.com').then(function (res) {
  // do something else
})

request('https://github.com').then(function (res) {
  // handle same res object (or copy, if options.clone === true)
})

Unfinished Business

Might add a caching option if I end up needing it, so that request results aren't immediately thrown away after the async function finishes

Add support for generators and thunks (probably already works but need to test)