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

invocation-list

v0.1.3

Published

A module that supports binding multiple functions to a name using ES7/TypeScript decorators.

Downloads

2

Readme

Invocation Lists

This is a small library that can be used with ES7/TypeScript decorators. It lets you specify that a function should be executed when another one is executed. You can do this multiple times, creating invocation lists under a single function that are inherited using standard JavaScript prototype inheritance.

Here is how it looks like in practice:

import {invokedBy} from 'invocation-list';
let a = "";
class Example {
	
	hello() {
		a += "0";
	}

	@invokedBy('hello');
	method1() {
		a+= "1";
	}
	
	@invokedBy('hello')
	method2() {
		a+= "2"
	}
}

let example = new Example();
example.hello();
expect(a).toBe("012");

In the above example, method1 and method2 were added to the 'invocation list' of hello, which includes the body of the original method at the beginning.

This plays well with JavaScript prototype inheritance.

class Derived extends Example {
	@invokedBy('hello');
	method3() {
		a += "3";
	}
}

The above modifies the invocation list for hello only for objects of Derived.

However, note that if you override the managed method in a more derived prototype:

class Derived extends Example {
	hello() {

	}
}

The member is no longer managed by the invocation list of less-derived prototypes and they don't interfere with the new functionality.

Now, you can keep using invokedBy on that member, but overriding hello essentially blocked off the older invocation lists.

class Derived extends Example {
	hello() {
		a += "0";
	}
	@invokedBy('hello')
	method4() {
		a += "4";
	}
}
new Derived().hello();
expect(a).toBe("04");

Things would've been okay if we'd added a super call:

class Derived extends Example {
	hello() {
		super.hello();
	}
	@invokedBy('hello')
	method4() {
		a += "4";
	}
}
new Derived().hello();
expect(a).toBe("01234");

Motivation

The motivation of this library is to allow syntax like this when working with React:

class ExampleComponent extends React.Component {
	@Lifecycle.componentWillUpdate
	@Lifecycle.componentWillMount
	doStuff() {
	}
}

This is implemented in another library.