npm-i-progress

npm-i-progress

Run npm install with a live progress bar based on real fetch/extract events from npm’s --verbose output.
No fake timers — the total grows as sub-dependencies are discovered.

✨ Features

• Real-time progress while npm install runs
• Single, continuous bar (no flicker on warnings)
• Pass-through flags (--legacy-peer-deps, package names, etc.)
• Works anywhere in your projects

🚀 Install

Global (recommended):

npm i -g npm-i-progress

One-off:

npx npm-i-progress

🧭 Usage

Inside any Node project directory:

npm-i-progress

Or use the short alias:

npi

Pass through any args you’d normally give npm install:

npm-i-progress --legacy-peer-deps
npm-i-progress react react-dom

🧰 How it works

This CLI spawns:

npm install --verbose

and parses lines that indicate fetch/resolve (to grow the total) and extract/install (to increment completed).
The bar updates continuously without resetting on warnings.

Note: npm doesn’t expose an official progress API.
This uses heuristic parsing and may vary slightly by npm version.
If your logs look different, please open an issue with a snippet.

📦 Requirements

• Node.js 16+

🤔 FAQ

Does it replace npm install?
No. It wraps npm install and shows progress; it passes through args and exit codes.

Can I use it in CI?
Yes, but progress bars aren’t very useful in plain logs.
(A future update may auto-disable when CI=true.)

Why does total package count grow while running?
npm discovers sub-dependencies as it resolves the tree, so the total increases dynamically — that’s expected and more accurate than a fixed guess.

🧹 Uninstall

npm un -g npm-i-progress

🐞 Troubleshooting

• Bar doesn’t move for a while: Some registries are slow; it should advance when extraction starts.
• Weird npm output: Please paste a few lines of --verbose output in an issue; we’ll expand our matchers.
• Windows PowerShell: If execution policy blocks global bins, run your terminal as Administrator or adjust policy.

📝 License

MIT © 2025 Mohammed Suhail Roushan Ali