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

composable-js

v0.1.12

Published

Allows referencing overridden properties of classes using decorators regardless of order

Downloads

10

Readme

Composable-js

Use cases

This package enables programmer to not care about the order of referencing and overriding decorators for constructors and methods.

In following example the result of the console.log will be 1.

let a: any;

function referencingDecorator(object: any, propertyName: string, descriptor: PropertyDescriptor) {
    a = descriptor.value;
}

function overridingDecorator(object: any, propertyName: string, descriptor: PropertyDescriptor) {
    descriptor.value = (...args: any[]) => 1;
}

class ExampleClassA {
    @referencingDecorator
    @overridingDecorator
    exampleMethod() {
        return 0;
    }
}

console.log(a());

On the other hand, if we swap the order of the decorators, we get 0.

//...
@overridingDecorator
@referencingDecorator
exampleMethod()
{
    return 0;
}

//...

This happens because of a being a reference of the original function, not the overridden one. Same principle applies to constructors.

Composable-js aims to solve this problem.


let a: any;

function referencingDecorator(originalFunction: Function, composedFunction: Function) {
    a = composedFunction;
    return originalFunction
}

function overridingDecorator() {
    return (...args: any[]) => 1;
}

class ExampleClassA {
    @ComposableFunction.decorator(referencingDecorator)
    @ComposableFunction.decorator(overridingDecorator)
    exampleMethod() {
        return 0;
    }
}
console.log(a());

class ExampleClassB {
    @ComposableFunction.decorator(overridingDecorator)
    @ComposableFunction.decorator(referencingDecorator)
    exampleMethod() {
        return 0;
    }
}


console.log(a());

Using the composable function API the order of decorators is negated in terms for referencing. a will always call the final function, not the intermediary.

Usage

Composable-js exposes to APIs - ComposableClass and ComposableFunction.

static decorator<T>(transformation:(original:T,composed:T) => T) method allows easy decorator creation by providing a transformation function, where T is either a constructor or a function.

You can also use the direct method of getting instance of ComposableClass or ComposableFunction assigned to particular constructor or function by calling get<T>(value:T). The returned instance of the class has composed property which is the current version of the overridden function and chain<T>(transformation:(original:T,composed:T) => T) which allows for manual chaining.

Contribution

Feel free to create merge requests or issues, I'll look at them as fast as I can.