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

waterfall-cli

v1.0.0-alpha.10

Published

Effortlessly create CLIs powered by Node.js

Downloads

272

Readme

Waterfall CLI

TODO

Quick start

TODO

Documentation

Read the docs at: https://waterfallcli.io/docs/

Comparison

TODO

Contributing

We love contributions! Contributing is easy; learn how.

Notes for future documentation:

The printError() function prints a message in a standardized way. The message will be sent to stderr, and it is possible that this might appear before un-flushed content in the stdout stream has been flushed. So, care may be needed to ensure stdout is flushed before calling printError() if you want the error message to always appear last. Also, it's your responsibility what happens after the message is output. ie: If you want to exit the program, and you're not within asynchronously executed code, you might be fine using process.exit() to immediately exit. But, if within asynchronous or callback code, you will likely find that process.exit() does not immediately exit, but instead, the 'exit' is scheduled for execution after currently executing code is done, so you'll need to use other flow control approaches (eg: return or throw an Error) to prevent subsequent code from executing.