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

simple-cli-prompter

v0.0.9

Published

Simple utility for prompting the user for input in a CLI environment

Downloads

1,535

Readme

This repo contains simple utility methods for promting the user for input in a CLI application. There is deliberately only a few different types of prompts that behave consistently and are easy to use (both for the end-user and the developer).

When there are options to select you can always type to search for the option you want.
The search is case-insensitive and looks for subsequences, e.g. to find the item This is a test you can type is test, which will match (and highlight) is and test in the item.

API

There are 4 methods for prompting users for input.

ask

export type Choice = { message?: string; name: string; hint?: string };

export type StringOrChoice = string | Choice;

export async function ask(
  text: string,
  choices?: StringOrChoice[],
): Promise<string>;

The ask function prompts the user for a string, and if the choices parameter is provided, the user can only select one of the provided options. The selected option is returned as a string.

If using the Choice type the name field is the value that is returned when the user selects the option, and message and hint are used to display the option to the user.

confirm

export async function confirm(
  message: string,
  defaultChoice = true,
  secondsTimeout = 0,
): Promise<boolean>;

The confirm function prompts the user for a boolean value, and if the secondsTimeout parameter is provided the default choice is used after the timeout has passed.

file

export async function file(text: string, ext?: string, cwd?: string): Promise<string>;

The file function prompts the user for a file path, and if the ext parameter is provided the user can only select files with the provided extension. cwd is used as the base directory for the file path. It defaults to the current working directory.

multiple

export async function multiple(
  text: string,
  choices: StringOrChoice[],
  requiredAtLeastOne = true,
): Promise<string[]>;

Similar to ask but allows the user to select multiple options. Tapping the space key toggles the selection of the currently highlighted option.

logAbove

export function logAbove(str: string): void;

There is additionally a utility function logAbove that logs a string above current prompting UI. Simply logging a string using console.log(...) will overwrite the prompting UI, so this function has to be used if a user might be actively interacting with a prompt.

Guidelines for application developers

  • Provide options to select from whenever possible.
    The UI scales to an absurd amount of options, so it's fine to present a UI where there are thousands of options to select from.
  • Prepare things in the background using promises.
    Heavy work can often be prepared in the background. E.g. in the example app (see exampleApp) a git repository is cloned in the background while the user is prompted for what to do.
  • async all the things! Any synchronous IO that happens while the user is prompted will block the UI.