progress
npmv2.0.3Flexible ascii progress bar
Not recommended for new projects
No — progress should not be adopted for new projects. Last published 2835 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2835 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 15 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 4 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding progress to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=0.4.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the progress README.
var ProgressBar = require('progress');
var bar = new ProgressBar(':bar', { total: 10 });
var timer = setInterval(function () {
bar.tick();
if (bar.complete) {
console.log('\ncomplete\n');
clearInterval(timer);
}
}, 100);progress vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| progressthis page | 0 | 2 | MIT | 7 years ago |
| cli-spinners | 0 | 1 | MIT | 1 day ago |
| ora | 0 | 6 | MIT | 1 day ago |
| commander | 451.1M | 11 | MIT | 1 day ago |
| cliui | 212.4M | 1 | ISC | 1 day ago |
| yargs-parser | 178.8M | 2 | ISC | 1 day ago |
Used by
Popular packages that depend on progress.
Relationship graph
Dependencies (left) and dependents (right) of progress.
Frequently installed together
The Expo SDK
Expo Router is a file-based router for React Native and web applications.
Lightweight debugging utility for Node.js and the browser
TypeScript definitions for node
The semantic version parser used by npm.
the most correct and second fastest glob implementation in JavaScript
TypeScript-first schema declaration and validation library with static type inference
Better streaming static file server with Range and conditional-GET support
Create clickable links in the terminal
A library for interacting with the app.json
Best-effort discovery of the machine's default gateway and local network IP exclusively with UDP sockets.
A high-level API to automate web browsers
Release history
No releases in the last two years, typically about 47 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.3latest | 7 years ago | 15 KB | MIT |
| 2.0.2 | 7 years ago | 15 KB | MIT |
| 2.0.1 | 8 years ago | 15 KB | MIT |
| 2.0.0 | 9 years ago | — | MIT |
| 1.1.8 | 12 years ago | — | MIT |
| 1.1.7 | 12 years ago | — | MIT |
| 1.1.6 | 12 years ago | — | MIT |
| 1.1.5 | 12 years ago | — | MIT |
| 1.1.4 | 12 years ago | — | MIT |
| 1.1.3 | 12 years ago | — | MIT |
| 1.1.2 | 13 years ago | — | MIT |
| 1.1.0 | 13 years ago | — | MIT |
| 1.0.1 | 13 years ago | — | MIT |
| 1.0.0 | 13 years ago | — | MIT |
| 0.1.0 | 14 years ago | — | MIT |
Overview
progress is an npm package that flexible ascii progress bar. It has 2 known dependents in the graph. The latest version is 2.0.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need flexible ascii progress bar and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Zero runtime dependencies — minimal footprint.
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use progress?
No — progress should not be adopted for new projects. Last published 2835 days ago.
How do I install progress?
Run `npm install progress` to add progress to your npm project.
What license is progress released under?
progress is distributed under the MIT license.
How popular is progress?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on progress.
Is progress still maintained?
The most recent release of progress (v2.0.3) was published 7 years ago.
Does progress run install scripts?
No. progress does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.