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 🙏

© 2025 – Pkg Stats / Ryan Hefner

secretary

v0.1.0

Published

Bring common sense to console logging.

Readme

#secretary#

A node.js module that brings common sense to console logging.

##Installation##

Not quite published yet

##Setup##

####Configuration:####

sec.configure({
    minFlag: 1,
    maxFlag: 5,
    minRunningFlag: 3,
    maxRunningFlag: 4
});

The potential configuration options are as follows:

  • minFlag - default: 1 - The lowest possible flag for any output. This must be >= 1.
  • maxFlag - default: 10 - The highest possible flag for any output. This must be >= 1.
  • minRunningFlag - default: minFlag - The lowest flag whose output will be processed when the program is run. This value must fall within the range of the minFlag and the maxFlag or it will not be registered.
  • maxRunningFlag - default: maxFlag - The highest flag whose output will be processed when the program is run. This value must fall within the range of the minFlag and the maxFlag or it will not be registered.

##Usage##

####Instantiation:####

var sec = require('secretary');

####Filtering:####

One of the key features of secretary is the ability to ~~litter your code with~~ thoughtfully place console logging throughout your code, and have it filtered out at runtime by the flag that was supplied with the output. This way, you're always in control of the verbosity of your output, during development and during production. It also does away with the need for quick-and-dirty console.logs that you delete shortly afterwards.

If we assume the following configuration:

minFlag: 1,
maxFlag: 5,
minRunningFlag: 3

And then run the following code:

sec.log('Beginning DEBUG output...', 1);
sec.log('Integrity check successful', 3);
sec.log('Server starting on port 3000', 5);

We will see the following output:

Integrity check successful
Server starting on port 3000