async-foreach
npmv0.1.3An optionally-asynchronous forEach with an interesting interface.
Not recommended for new projects
No — async-foreach should not be adopted for new projects. Last published 4832 days ago. No license declared — you have no explicit right to use this code.
- BAdoption: grade B, Good.
745.8K downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 4832 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
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 async-foreach 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 *
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the async-foreach README.
var forEach = require('async-foreach').forEach;
forEach(["a", "b", "c"], function(item, index, arr) {
console.log("each", item, index, arr);
});
// logs:
// each a 0 ["a", "b", "c"]
// each b 1 ["a", "b", "c"]
// each c 2 ["a", "b", "c"]async-foreach 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 |
|---|---|---|---|---|
| async-foreachthis page | 745.8K | 1 | — | 13 years ago |
| quansync | 16.7M | 1 | MIT | 4 hours ago |
| p-locate | 0 | 1 | MIT | 4 hours ago |
| locate-path | 289.8M | 1 | MIT | 4 hours ago |
| regenerator-runtime | 65.8M | 4 | MIT | 4 hours ago |
| lie | 47.4M | 1 | MIT | 4 hours ago |
Used by
Popular packages that depend on async-foreach.
Relationship graph
Dependencies (left) and dependents (right) of async-foreach.
Frequently installed together
An AST-based pattern checker for JavaScript.
Opinionated, caching, retrying fetch client
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
Given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem.
Parse sass files and extract a graph of imports
Lodash modular utilities.
Non-blocking stdout stream
Cross platform child_process#spawn and child_process#spawnSync
the most correct and second fastest glob implementation in JavaScript
A globbing fs.watch wrapper built from the best parts of other fine watch libs.
CLI app helper
Release history
No releases in the last two years.
| Version | Published | Size | License |
|---|---|---|---|
| 0.1.3latest | 13 years ago | — | — |
| 0.1.2 | 14 years ago | — | — |
Overview
async-foreach is an npm package that an optionally-asynchronous forEach with an interesting interface. It is very popular, with about 745.8K downloads per week and 1 known dependents in the graph. The latest version is 0.1.3.
Who should use it
Teams working in the npm ecosystem who need an optionally-asynchronous forEach with an interesting interface and value a battle-tested, widely-adopted 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
- Large, well-established user base (745.8K weekly downloads).
- Zero runtime dependencies — minimal footprint.
Cons
- No bundled TypeScript types (may require a separate @types package).
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use async-foreach?
No — async-foreach should not be adopted for new projects. Last published 4832 days ago. No license declared — you have no explicit right to use this code.
How do I install async-foreach?
Run `npm install async-foreach` to add async-foreach to your npm project.
What license is async-foreach released under?
No license was detected in async-foreach's metadata; review the repository before use.
How popular is async-foreach?
async-foreach has approximately 745,824 downloads per week and 1 known dependent packages.
Is async-foreach still maintained?
The most recent release of async-foreach (v0.1.3) was published 13 years ago.
Does async-foreach run install scripts?
No. async-foreach does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.