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

named-dep-counter

v0.6.1

Published

Like DepCounter ( dep_counter) but with names for the dependencies

Downloads

1

Readme

NamedDepCounter (named-dep-counter)

Version 0.6.1 BETA

NamedDepCounter is a tool to keep track of a series of dependencies to be completed. It can be used to track a series of tasks that need to be completed.

NamedDepCounter will track:

  • The number of total dependencies that need to be completed.
  • The number of dependencies that have already been completed.
  • The number of dependencies that need to be completed.

... If that is all you need to do, look into DepCounter

NamedDepCounter will ALSO track:

  • The names of the dependencies that need to be completed.
  • The names of the dependencies that have already been completed.
  • The names of the dependencies that need to be completed.

Install:

    npm install named-dep-counter

QuickStart:

    import NamedDepCounter from 'named-dep-counter';
    const namedDepCounter = new NamedDepCounter('depCounterName');

    namedDepCounter.dependencies(['one', 'two', 'three']);
    // same as namedDepCounter.deps(['one', 'two', 'three']);
    console.log(namedDepCounter.ready()); // false
    console.log(namedDepCounter.current()); // [];
    console.log(namedDepCounter.currentCount()); // 0
    console.log(namedDepCounter.remaining()); // ['one', 'two', 'three'];
    console.log(namedDepCounter.remainingCount()); // 3

    namedDepCounter.mark('one');
    console.log(namedDepCounter.ready()); // false
    console.log(namedDepCounter.current()); // ['one'];
    console.log(namedDepCounter.currentCount()); // 1
    console.log(namedDepCounter.remaining()); // ['two', 'three'];
    console.log(namedDepCounter.remainingCount()); // 2

    namedDepCounter.mark('one'); // ignores this since 'one' was already marked.

    namedDepCounter.mark('two');
    namedDepCounter.mark('three');
    console.log(namedDepCounter.ready()); // true
    console.log(namedDepCounter.current()); // ['one', 'two', 'three'];
    console.log(namedDepCounter.currentCount()); // 3
    console.log(namedDepCounter.remaining()); // [];
    console.log(namedDepCounter.remainingCount()); // 0

Add some callbacks:

    import NamedDepCounter from 'named-dep-counter';
    const namedDepCounter = new NamedDepCounter('namedDepCounterName');
    namedDepCounter.onComplete((namedDepCounter)=>console.log('DONE', namedDepCounter.ready()));
    namedDepCounter.onMark((namedDepCounter, key)=>console.log(`Mark! ${key}))

    namedDepCounter.mark('one');  // 'Mark! one'
    namedDepCounter.mark('one');  // NO EVENT
    namedDepCounter.mark('two');  // 'Mark! two'
    namedDepCounter.mark('three');  // 'Mark! three' & 'DONE true'

Alter the context for the callbacks with self command.

The first argument for every callback is 'self'. By default, 'self' is the instance of the NamedDepCounter itself. You can override this if, for instance you are nesting the NamedDepCounter inside another class instance.

    const namedDepCounter = new NamedDepCounter('fricassee');
    namedDepCounter.self({TYPE: 'SELFY'});
    namedDepCounter.onComplete((self)=>console.log(self.TYPE + '_complete'));
    namedDepCounter.deps(['a', 'b']);
    namedDepCounter.onMark((self, key)=>console.log(self.TYPE + key))
    namedDepCounter.mark('a'); // logs SELFY_a;
    namedDepCounter.mark('b'); // logs SELFY_b AND logs SELFY_complete