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

npmi.js

v1.0.2

Published

Command Line Application that allows a user to run `npm i` on all adjacent folders.

Downloads

5

Readme

npm Downloads Shield Stars Shield Forks Shield Contributors Shield License Shield LinkedIn Shield

npm install -g npmi.js

About The Project

npmi.js is an npm package that allows a user to run the command npm install on multiple folders at the same time. The main advantage of this is that if you have multiple projects that take very long to run npm i on, you don't have to sit and wait for:

  1. Wait for a single project to install
  2. Change to the next project
  3. Run the install on the next project
  4. Repeat for all projects

Using npmi.js you simply move all projects into one parent folder, run the command npmijs from the terminal, and let your computer do its thing. Essentially cutting out the time waiting for one install to finish in order to manually start the next install.

Installation

npmi.js is meant to be globally installed to your device. To globally install run this command:

npm install -g npmi.js

If you would like to verify the download run npm list -g and you should see [email protected] pop up.

Usage

Once you have npmi.js installed globally, collect all the files you would like to run npm install on into a parent folder. Navigate to the parent folder in your terminal and use the command:

npmijs

Running the command npmijs will check all folders and subfolders to see if they contain a package.json. If the folder does, it will run npm i in that location. It will then repeat this process for all files provided.

Once the process is completed if you would like to verify everything has installed, check your files to see if they have /node_modules and a package_lock.json.

Example Usage

Parent-Directory/
├── Project-1/
│   ├── index.js
│   └── package.json
├── Project-2/
│   ├── client/
│   │   ├── client.js
│   │   └── package.json
│   ├── server/
│   │   ├── server.js
│   │   └── package.json
│   └── package.json
├── Project-3/
│   ├── Solved/
│   │   ├── index.js
│   │   └── package.json
│   └── Unsolved/
│       ├── index.js
│       └── package.json
├── Project-4/
│   └── subfolder/
│       └── subfolder2/
│           ├── index.js
│           └── package.json
└── Project-5/
    └── index.js

In this example we have 5 project folders within a parent folder named Parent-Directory. Each project gives an example situation that might occur.

  1. Project-1 contains a package.json on the root level
    • Output: npmi.js will run npm i
  2. Project-2 contains a package.json on the root level, and another package.json within > the client/ and server/ folders respectively
    • Output: npmi.js will run npm i on all 3 folders
  3. Project-3 does not contain a package.json on the root level, but does within the /Solved and /Unsolved folders
    • Output: npmi.js will run npm i on the /Solved and /Unsolved folders
  4. Project-4 does not contain a package.json on the root level, no package on the /subFolder level, and a package on the /subfolder2 level
    • Output: npmi.js will do nothing. npmi.js only looks for a package.json 1 folder deep into each project.
  5. Project-5 does not contain a package.json at all
    • Output: npmi.js will do nothing

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Mateo Wallace - GitHub - Email - LinkedIn - Portfolio - npmi.js repo