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

screen-renderer

v0.1.1

Published

a CLI tool to help render regions of the screen

Downloads

7

Readme

Introduction

This library was created to ease updating the screen for CLI tools that need to show progress of their actions.

The concept is that only part of the information changes so the library stores the state of the whole date and calls a user defined function to render the screen when something changes.

Usage

See examples

var ScreenRenderer = require( 'screen-renderer' );

var sr = new ScreenRenderer( <render function> );

The render function receives an 'out' function to use for output strings and a params object that contains all the parameters received via the update function incrementally.

function render( _out , _params ) {
  _out( 'Current Value:' , _params.param1 );
}

The update method allows you to update some or all the parameters used by the render function for rendering the screen. By default it triggers a screen update, but you can suppress that by sending a second parameter to false in case you want to make multiple updates before rendering

sr.update( params , should_render )
  • params - object of parameters used by the render function.
  • should_render - bool, default true. should the update trigger a render of the screen