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

ninstall

v1.1.2

Published

A CLI tool to install the same npm modules that you always install

Downloads

6

Readme

ninstall

Build Status

A CLI tool to install the same npm modules that you always install

Do you always install the same npm modules on your project every time? ninstall can help you with that. You can save multiple configurations, for different types of projects you save. So if you have saved a configuration, you can npm install the same modules on new projects.

Installation

> npm install -g ninstall

Usage

New Installation

Install from Saved Configuration

Setup

In order for ninstall to work, your home directory must be setup. ninstall will place your configuration file in your $HOME/%HOME%``/.savedConfig.json

New Installation

Input Files

When running to install for the first time, or to get a new configuration, run

> ninstall new

First, you will be prompted for node module that you're saving. These are the modules that you would npm install --save.

Please input the files you would like to save for your module's use. Seperate your files with a space.
? Input your --save files:  

If you want to save multiple files, input them with a space

? Input your --save files: kontains xcept git-lib

The next prompt is for the node modules you are using for your development. These are modules that you would npm install --save-dev

Please input the files you would like to save for your module's development use. Seperate your files with a space.
? Input your --save-dev files:  

You will be prompted for a confirmation next. Selecting Y will install the modules.

Saving Configuration

After installation is complete, you will be prompted for if you want to save the configuration. If you selected to save it, it means the next time, the same modules and dev modules will be saved as well.

? Would you like to save this configuration? (Y/n) 

If you select Y, you will be prompted for a configuration name.

? Please input the name you want to save in this configuration:

The name you input for the configuration will be the one you refer to if you want to install the same configuration next time.

For Example: If your configuration is name testConfig01, then running ninstall testConfig0 next time will install the same modules and development modules you installed this time.

Install from Saved Configuration

If you have ran ninstall new previously and saved the configuration, then can use these configurations to install onto new node projects. This is handy when you create multiple types of node modules, but many of them share similar node modules. That way, you can ninstall it once, save the configuration, then run it again so you can install the same modules on a new module.

Select Previous Configuration

To run from a saved configuration, you can run

> ninstall

and you will be prompted to select a list of configurations that you have previously saved.

? Please select the configuration you would like to install:  (Use arrow keys)
❯ normalNpm
  npmServer

Install from Commandline

If you know the previous configuration name, you can run

> ninstall [config name]

Example

> ninstall normalNpm

Version

1.1.0

  • Modified configJson.json location to HOME directory

1.0.0

  • First working publish