neo-async
npmv2.6.2Neo-Async is a drop-in replacement for Async, it almost fully covers its functionality and runs faster
Not recommended for new projects
No — neo-async should not be adopted for new projects. Last published 2253 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2253 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 291 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- 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 neo-async 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
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the neo-async README.
<script src="async.min.js"></script>neo-async 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 |
|---|---|---|---|---|
| neo-asyncthis page | 0 | 3 | MIT | 6 years ago |
| @open-draft/until | 0 | 1 | MIT | 1 day ago |
| until-async | 0 | 1 | MIT | 1 day ago |
| type-fest | 337.8M | 6 | (MIT OR CC0-1.0) | 1 day ago |
| p-limit | 293.1M | 5 | MIT | 1 day ago |
| p-locate | 216.9M | 1 | MIT | 1 day ago |
Dependencies
Declared by neo-async v2.6.2. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (27)
Used by
Popular packages that depend on neo-async.
Fast, in memory work queue
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.
Relationship graph
Dependencies (left) and dependents (right) of neo-async.
Frequently installed together
An AST-based pattern checker for JavaScript.
React is a JavaScript library for building user interfaces.
React package for working with the DOM.
ECMAScript parser
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
TypeScript definitions for estree
Lodash modular utilities.
Prettier is an opinionated code formatter
Node's event emitter for all engines.
Delightful JavaScript Testing.
A library to create a trace of your node app per Google's Trace Event format.
WebAssembly binary format parser
Release history
No releases in the last two years, typically about 43 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.6.2latest | 6 years ago | 291 KB | MIT |
| 2.6.1 | 7 years ago | 290 KB | MIT |
| 2.6.0 | 8 years ago | 290 KB | MIT |
| 2.5.2 | 8 years ago | 284 KB | MIT |
| 2.5.1 | 8 years ago | 283 KB | MIT |
| 2.5.0 | 9 years ago | — | MIT |
| 2.4.0 | 9 years ago | — | MIT |
| 2.4.0-0 | 9 years ago | — | MIT |
| 2.3.0 | 9 years ago | — | MIT |
| 2.2.2 | 9 years ago | — | MIT |
| 2.2.0 | 9 years ago | — | MIT |
| 2.1.0 | 9 years ago | — | MIT |
| 2.0.1 | 10 years ago | — | MIT |
| 2.0.0 | 10 years ago | — | MIT |
| 2.0.0-rc.1 | 10 years ago | — | MIT |
Overview
neo-async is an npm package that neo-Async is a drop-in replacement for Async, it almost fully covers its functionality and runs faster. It has 3 known dependents in the graph. The latest version is 2.6.2, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need neo-Async is a drop-in replacement for Async, it almost fully covers its functionality and runs faster and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, 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).
Cons
- Large dependency tree (27 direct dependencies) increases install size and audit surface.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use neo-async?
No — neo-async should not be adopted for new projects. Last published 2253 days ago.
How do I install neo-async?
Run `npm install neo-async` to add neo-async to your npm project.
What license is neo-async released under?
neo-async is distributed under the MIT license.
How popular is neo-async?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on neo-async.
Is neo-async still maintained?
The most recent release of neo-async (v2.6.2) was published 6 years ago.
Does neo-async run install scripts?
No. neo-async does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.