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

status-logger

v3.1.1

Published

print updating progress to console and stdout

Downloads

2,337

Readme

Status Logger

Manage complex CLI output with arrays and automatically print any changes to stdout via ansi-diff-stream.

WARNING: Awesomeness elsewhere. status-logger was nice but it wasn't enough, it still felt like node but I wanted frontend javascript fun. Introducing... 🥁 ... neat-log. neat-log is much neater and I'd definitely recommend using that. It uses status-logger under the hood.

Example

The example here will initially print:

Status Logger Example:
starting...

Then once it gets started, it will print the time every second:

Status Logger Example:
Time = 10 seconds
var output = ['Status Logger Example:', 'starting...']
var log = statusLogger(output)
setInterval(function () {
  log.print()
}, 100)
log.print()
start()

function start () {
  var sec = 0
  setInterval(function () {
    sec++
    output[1] = `Time = ${sec} seconds`
  }, 1000)
}

Run node basic-example.js or node example.js to see full examples. You can find more complex usage in these modules:

Installation

npm install status-logger

API

var log = statusLogger(messages, opts)

messages is an array with of lines to print. They will be printed in order with a newline spacer between each. Message arrays are flattened so they can be any mix of nested arrays and strings.

Options

  • quiet: do not print anything
  • debug: print everything to console.log or console.error

log.print()

Print messages from all groups.

var output = log.clear(messages)

Clear all output and create a empty output array (or with new messages).

log.diff

ansi-diff-stream instance

log.messages

Stored reference to the original messages array.

License

MIT