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

console-ui

v3.1.2

Published

common interface for abstracting a console ui

Downloads

563,739

Readme

console-ui

Build Status Build status

The goal of this library is to declare a common interface that various node_modules can utilize allowing their UI interactions to be well coordinated and interoperable. This repo provides reference UI and test mock implementations. In theory, an alternate implementation abiding by the describe API could be provided, and the system and all participating libraries would continue to function correctly.

Features:

  • unified and pluggable input/output streams for all participants
  • system wide writeLevels enabling ability to easily silence/warn/debug print while abiding by shared configuration
  • unified progress
  • unified CI state (to disable CI unfriendly features such as progress spinners)
  • simple
  • test mock

Usage

const UI = require('console-ui')
const ui = new UI({
  inputStream: process.stdin,
  outputStream: process.stdout,
  errorStream: process.stderr,
  writeLevel: 'DEBUG' | 'INFO' | 'WARNING' | 'ERROR',
  ci: true | false
});

write to output:

ui.write('message');
ui.write('message', 'ERROR'); // specify  writelevel

write + newline to output:

ui.writeLine('message');
ui.writeLine('message', 'ERROR'); // specify  writelevel

write + newline to stderr;

ui.writeErrorLine('message');

write with DEBUG writeLevel

ui.writeDebugLine('message');

write with INFO writeLevel

ui.writeInfoLine('message');

write with WARN writeLevel

ui.writeWarnLine('message');

write a message related to a deprecation

ui.writeDeprecateLine('some message', true | false); // pass boolean as second argument indicating if deprecated or not

write an error nicely (in red) to the console:

  • if error.file || error.filename, nicely print the file name

    • if error.line also nicely print file + line
    • if error.col also nicely print file + line + col
  • if error.message, nicely print it

  • if error.stack, nicely print it

ui.writeError(error);

to adjust the writeLevel on the fly:

ui.setWriteLevel('DEBUG' || 'INFO' || 'WARNING' || 'ERROR');

to begin progress spinner \w message (only if INFO writeLevel is visible)

ui.startProgress('building...');

to end progress spinner

ui.stopProgress();

to prompt a user, via inquirer

ui.prompt(queryForInquirer, callback);

to query if a given writeLevel is visible:

ui.writeLevelVisible('DEBUG' || 'INFO' || 'WARNING' || 'ERROR'); // => true | false