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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sorrell/listr

v1.0.1

Published

Terminal task list reborn! Create beautiful CLI interfaces via easy and logical to implement task lists that feel alive and interactive.

Readme

© 2026 Gage Sorrell et al. Released under the MIT license.

@sorrell/listr

This is a fork of listr2. It removes the following features,

  • multiple renderers (it retains only the ListrDefaultRenderer)
  • exitOnError?: boolean; option

and adds the following features,

Documentation

tensed?: boolean;

If the tensed property is true for a given task, then its title will be required to begin with a present participle--that is, a verb that ends with ing (this is enforced by the type system). If the task ends successfully, then the starting verb is changed to its simple past tense form; if it fails, then the "Failed to " is prepended to the title, its starting verb is uncapitalized, and the starting verb is changed to its unconjugated form. An optional Exit return strategy is given, which allows you to specify a custom title. See §Return Strategy for more details.

Return Strategy

All tasks must return one of the values belonging to the member property Listr.Return. Its properties are summarized below.

Success

Return this value to indicate that the task completed successfully. This will cause the task's title to be set as described in §tensed?: boolean;.

Failure(Die: TaskDeath = false)

Return this value to indicate that the task completed erroneously. If Die.Die === true, then the parent task will exit early. Other options are described in §TaskDeath.

TaskDeath
  • @property Die - Whether the parent task should exit early.
  • @property Completely - If supplied, and Die === true, then the root task will exit.
  • @property Message - If Die === true, then this message will be displayed below the tasks. The static property Listr.DeathMessagePrefix is prepended to the message (with a space). Ignored if Completely === false or if the parent task is not the root task.
  • @property TaskTitle - If supplied, and Die === true, then the task's title will become this.
type TaskDeath =
    | false
    | {
        Die: false;
    }
    | {
        Die: boolean;
        Completely?: boolean;
        Message?: string;
        TaskTitle?: string;
    }
    | {
        Die: true;
        Completely?: boolean;
        Message: string;
        TaskTitle?: string;
    };

Return this value to indicate that the task completed erroneously.

This will cause the task's title to be set as described in §tensed?: boolean;.

Exit(CustomTitle: string, State?: ListrDefaultRendererLogLevels);

Return a call to this function to indicate that the task ended in a nontrivial state, such that the title becomes a CustomTitle to convey this final state, which is something other than the expected, simple success or failure.

Subtasks<NewContextType>(Subtasks: TMaybeArray<ListrTask<NewContextType>>, Finally: (FinallyArgument: FinallyArgument<ContextType, NewContextType>) => SubtasksResult<ContextType>);

Return a call to this function to specify a set of subtasks, and a function that accepts the task in which this function was called, and returns a SubtasksResult, to determine (as a function of the parent tasks's and subtasks's contexts) whether the parent task succeeded or failed (or neither, in which case a custom title is returned).

FinallyArgument<ContextType, NewContextType>
  • @property Context - The context of the task from which Listr<ContextType>.Return.Subtasks was called.
  • @property SubtasksContext - The context of the subtasks.
  • @property ThisTask - The task containing the subtasks returned by calling Listr<ContextType>.Return.Subtasks, i.e., the parent task of the subtasks.
type FinallyArgument<ContextType, NewContextType> =
{
    Context: ContextType;
    SubtasksContext: NewContextType;
    ThisTask: ListrTask<ContextType>;
};
SubtasksResult

Identical to typeof Listr<ContextType>.Return, but without the Subtasks function, since this type exists to determine simply how the task containing the subtasks completed.

type SubtasksResult<ContextType> = Omit<ListrResult<ContextType>, "Subtasks">;

The original listr2 README.md may be found here.