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

factory-helper

v1.0.0

Published

A function prototype for easier constructors

Downloads

5

Readme

factory

This is a silly experiment, mostly.

Silly or not, the idea behind this is the opinion that this common js trick is not DRY, and is probably anti-pattern:

  function Thing(attr) {
    if (!(this instanceof Thing)) {
      return new Thing(attr);
    }
    ...
  }

It'd be better if we had an idiom that didn't necessitate repeating the name of the constructor three times.

This aims to solve the problem, but with the caveat that you cannot call the constructor recursively. Yet the only reason I usually see for calling a constructor recursively is to implement the above—the pain point that this module aims to eliminate in the first place. :)

However, I don't know if it's rubbish, and I've never used it at scale on a real project.

usage

  require('./factory.js').expose()

  var Robot = function (calibration) {
    this.calibration = calibration;
  }.factory();

  Robot.prototype.signal = function signal() {
    return this.calibration.signal;
  };

  Robot.prototype.attack = function attack(opponent) {
    console.log(this.signal(), ' > ', opponent.signal());
  };

  var bob = Robot({ signal: 'beep' });
  var bill = Robot({ signal: 'boop' });

  bob.attack(bill);
  bill.attack(bob);