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

babel-plugin-promote-class-properties

v0.0.1

Published

Babel plugin to replace old code using ClassProperties feature

Downloads

4

Readme

babel-plugin-promote-class-properties

Babel plugin to replace old code taking advantage of ClassProperties feature

Before

class Foo {
  constructor() {
    this.foo = this.foo.bind(this);
    this.bar = this.bar.bind(this);
  }

  foo(arg1, arg2) {
    console.log(arg1, arg2)
  }

  bar(lol) {
    return lol;
  }
}

After

class Foo {
  foo = (arg1, arg2) => {
    console.log(arg1, arg2)
  }

  bar = (lol) => {
    return lol;
  }
}

Installation

Motivation

Declaring event listeners is a common thing to do on the daily bases of every JS developer. In real life applications we see a lot of this:

class App extends React.Component {
  constructor() {
    this.onLoad = this.onLoad.bind(this);

    this.state = {width: 0, height: 0};
  }

  onLoad({target: {height, width}}) {
    this.setState({width, height});
  }

  render() {
    const {width, height} = this.state;

    return (
      <div>
        <div>{width}x{height}</div>
        <img onLoad={this.onLoad} />
      </div>
    );
  }
}

We need to do

this.onLoad = this.onLoad.bind(this);

Because of the way of this context is handled on addEventListener, see The_value_of_this_within_the_handler, from MDN:

If attaching a handler function to an element using addEventListener(), the value of this inside the handler is a reference to the element. It is the same as the value of the currentTarget property of the event argument that is passed to the handler.

Doing that reassignment, we keep the react component instance as this value and we can do operations like setState while still having access to the DOM element.

TODO

  • Remove empty constructor
  • Handle inline cases => <img onError={this.onImgError.bind(this) />
  • Handle => document.body.addEventListener('scroll', this.onScroll.bind(this));