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 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-plugin-prototype-chain

v0.1.1

Published

ESLint plugin to optimize prototype chain lookups

Readme

eslint-prototype-chain

ESLint rule to optimize prototype chain lookups

Summary

Repeatedly looking up values deep in the prototype chain can be less-than-performant--especially if getters are defined. Creating a variable to reference the value can speed things up.

This ESLint rule will tell you if you're doing this too much.

Installation

$ npm install -D eslint eslint-plugin-prototype-chain

Usage

Add this to your .eslintrc, assuming it's a JSON file:

{
  "plugins": [
    "prototype-chain"
  ],
  "prototype-chain/prototype-chain": [2, 1, 1]
}

The above configuration will cause an ESLint error when, in the same scope:

  • You use the same object member expression (foo.bar) OR the same "this" expression (this.bar) more than one (1) time (that's the 2nd array item), AND
  • You use one (1) member in the chain

A configuration such as this:

{
  "prototype-chain/prototype-chain": [2, 2, 3]
}

would cause an ESLint error when, in the same scope:

  • You use the same object member expression (foo.bar) OR the same "this" expression (this.bar) more than one (2) times, AND
  • You use one (2) members in the chain

That means repeating foo.bar will not throw an error. Repeating foo.bar.baz one time will not cause an error, but repeating it two times will.

Hope that makes sense!

Fair Warning

There are tests, but I haven't tried this against much real-world code yet.

License

© 2015 Christopher Hiller. Licensed MIT.