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

bind.for

v0.2.0

Published

A lazy Function.prototype.for(context) bind helper

Downloads

187

Readme

bind.for

Build Status Coverage Status

A lazy Function.prototype.for(context) bind helper.

This is an alternative take at the same problem bound-once would like to solve, except this should perform better for the following reasons:

  • the WeakMap is lazily created once per each method
  • because it's usually the method that binds multiple contexts, and not the other way around, this approach requires less moving parts
  • bound-once looks up for the method, either as function or as a string, then it weakly refers the context to a new Map, if not previously referenced, then it performs a lookup via such map to return the bound method, or it stores it in there once and return. bind.for here, looks up for the context right away, and it stores once the bind of itself if the content wasn't previously stored. This is one operation instead of 3.

By default, this module pollutes the Function.prototype with a lazy for method, but if that's not your cup of tea, you can include the ponyfill instead.

// global Function.prototype pollution
import 'bind.for';

const context = {};

method.for(context) === method.for(context);
method.for(context)() === context;

function method() {
  return this;
}

// clean ponyfill
import bindFor from 'bind.for/pony';

// will add the lazy `for` method
const fn = bindFor(function () { return this; });
fn.for(context) === fn.for(context);