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

clui-live

v0.3.4

Published

Simply update text on the terminal, even after subsequent output is written

Downloads

74

Readme

clui-live

Simply update text on the terminal, even after subsequent output is written

Running the demo file demo/demo.ts

Demo code available at demo/demo.ts

Installation

npm install --save clui-live

Usage

There are two ways to use this method. The first is to just use a single LiveArea and update it any time by calling the LiveArea#write() method. With this method, only one LiveArea can be active at each time.

import { LiveArea } from 'clui-live';

const area = new LiveArea();

for ( let i = 0; i < 100; i++ ) {
    area.write( 'Progress' + i );

    await sleepRandom();
}

// Closing the `LiveArea` will keep any text that was written to it last on screen and prevent any further updates. To avoid that, call area.clear().close() instead
area.close();

But sometimes we want to update more than one thing at the same time, and that's the really hard part. This module makes it easy though. Just create a LiveContainer and add as many LiveAreas to it as needed.

Note that when using a container, you can only use LiveAreas that belong to it. Using others will result in unexpected behavior.

import { LiveContainer, LiveArea } from 'clui-live';

const container = new LiveContainer();

// How to add an area to a container
const area1 = new LiveArea();

container.addLiveArea( area );

// A shortcut for that is
const area2 = container.createLiveArea();

for ( let i = 0; i < 100; i++ ) {
    // Update each area in an alternated way. They will both be updated in place
    // If the first area grew (or shrinked), the vertical positions of all areas below would adjust accordingly
    if ( i % 2 == 0 ) {
        area1.write( 'Progress' + i );
    } else {
        area2.write( 'Progress' + i * 2 );
    }

    await sleepRandom();
}

// Also, since the terminal doesn't allow to update text outside the viewport (when the text is above the buffer and you would
// have to scroll to see it), and so when any LiveArea falls off view, it's state is "forgotten" and when it updates next it 
// will be appended at the bottom.

But what about when other people use console.log? Doesn't that wreck things? Yes, but there is a simple fix for that: simply call LiveContainer#hook() when creating it.

const container = new LiveContainer().hook();

Sometimes you don't want to have to create a container and pass around references to it. In those instances you can use the global container (one that is lazily created when it is first used) by calling the hook() method on each live area (instead of calling it on a container) like so:

const area1 = new LiveArea().hook();
const area2 = new LiveArea().hook();