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

rename-this-keyword

v1.0.4

Published

Rename this keyword to create a smaller bundle at the end when uglify is applied.

Downloads

2

Readme

Rename-this

Why?

So, the idea to create this babel-plugin started when i saw one of my workmates' code which had a bunch of const _this = this and that was totally weird to me.

I went to him and asked why that type of variables, and then he explained me.

The real deal of doing this is because uglifyjs or any other minifier/uglifier does not reduce the name of this keyword, which ends up creating a bigger code, in terms of bytes.

Using babels website repl, if we choose the minify option.

Inserting the following code as input:

class Blah {
  constructor() {
    this.batman = '33';
    this.myFunction = this.myFunction.bind(this);
  }
  stubFunction() {
    const myProps = this.batman;
    if (this.batman === '123') {
      return null;
    }
  }
}

We are going to get the follow:

var Blah = (function() {
  function a() {
    _classCallCheck(this, a),
      (this.batman = "33"),
      (this.myFunction = this.myFunction.bind(this));
  }
  return (
    _createClass(a, [
      {
        key: "stubFunction",
        value: function stubFunction() {
          this.batman;
          if ("123" === this.batman) return null;
        }
      }
    ]),
    a
  );
})();

As you can see, this keyword remains the same, meaning that the file size will be a little bigger.

TODO: Insert uglify examples.

Roadmap

  • [ ] Write a better introduction and reasons why this was created.
  • [ ] Publish this direct into npm
  • [ ] Add more test cases

Must Update

  • There is a unknown issue that when it inserts a variable _then it also inserts a \n. Not that it is a major problem or something like that, uglify will remove blank spaces during build, but still an impovement.