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

save-instance

v1.4.5

Published

Make a class with member instances to get and save

Downloads

37

Readme

save-instance

NPM version build status Test coverage

Why save-instance

If you have a class like:

class Test {
    constructor (...args) {}
}

And you initialize some instances in a module (ie. a bootstrap module), like:

const a = new Test(...args);

Since you don't know what module would use them, you should export them by exports or global

Yet both exports and global seems not perfect for this case.

  • For exports, you should require that bootstrap module to use the instances, which is puzzle
  • For global, you should handle the namespace problem carefully

Maybe a better way is to bind the instances with the class itself, like:

const a1 = Test.getInstance('A');

Now it seems more reasonable, as "to get the Test instance named 'A' "

Of course, you should initalize and name it before using.

new Test(...args).saveInstance('A');
// or
Test.saveInstance('A', ...args);

How to use

Decoration is supposed as the best way to use this

const savable = require('save-instance');

@savable()
class Test {...}

Yet decorator is not implemented till current version (v7.6), use it like

class Test {...}
savable()(Test);

Other uses

Lazy mode

Maybe we want instances initialized in a lazy mode. Just use it like this:

Test.saveLazyInstance('A', ...args);

Singleton

Use default name '' to pretend as a singleton instance

new Test(...args).saveInstance();
const test =  Test.getInstance();

Options

If you want to preprocess arguments, use options.preprocessArguments(name, ...args)

@savable({
    preprocessArguments(name, ...args) {
        return ['arg1', 'arg2', 'arg3'];
    }
})
class Test {}

If you want to preprocess instance, use options.preprocessInstance(instance, name, ...args)

@savable({
    preprocessInstance(instance, name) {
        instance.name = name;
        return instance;
    }
})
class Test {}

If you want to set a default name, or want to map some names into one, use options.defaultName and options.map

@savable({
    defaultName: 'foo',
    map: {
        'bar': 'foo',
        'baz': 'foo',
    },
})
class Test {}

Notice that the default name is undefined and maps null to undefined.