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

@hagnerd/nps

v1.0.1

Published

A CLI for adding and modifying your npm scripts

Downloads

6

Readme

NPS

What is NPS?

NPS is a CLI for adding, modifying, extending, and overriding the scripts in your package.json file.

Why does NPS exist?

I wanted a way to quickly add, modify, extend, and override the scripts in my package.json files and I thought others might like the ergonomics as well.

Why not just open your package.json file and add the script?

Mostly laziness.

Usage

If you would like you can install globally using either yarn or npm.

npm install --global @hagnerd/nps
yarn global add @hagnerd/nps

After that it will be available with the command nps.

If you don't want to install the package globally, just run npx @hagnerd/nps.

What's next?

I'm thinking about adding some nice features like being able to easily select scripts to delete from the command line, saving a set of scripts to a template, and being able to add groups of scripts with one command.