promise
npmv8.3.0Bare bones Promises/A+ implementation
Not recommended for new projects
No — promise should not be adopted for new projects. Last published 1415 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1415 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 107 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 3 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 promise 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.
Licenses in the dependency tree
Every license you inherit by installing promise, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the promise README.
<script src="https://www.promisejs.org/polyfills/promise-6.1.0.js"></script>Dependencies
Declared by promise v8.3.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (6)
Used by
Popular packages that depend on promise.
Reactive Extensions for modern JavaScript
Leaner CSS
A framework for building native apps using React
A collection of utility libraries used by other Facebook JS projects
Throttle the parallelism of an asynchronous (promise returning) function / functions
Relationship graph
Dependencies (left) and dependents (right) of promise.
Frequently installed together
The semantic version parser used by npm.
An AST-based pattern checker for JavaScript.
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.
the most correct and second fastest glob implementation in JavaScript
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
TypeScript definitions for node
A comprehensive library for mime-type mapping
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
A drop-in replacement for fs, making various improvements.
Turn node's process.version into something useful.
A high-level API to automate web browsers
Generates and consumes source maps
Release history
No releases in the last two years, typically about 23 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 8.3.0latest | 3 years ago | 107 KB | MIT |
| 8.3.0-canary-5 | 3 years ago | 107 KB | MIT |
| 8.2.0 | 4 years ago | 101 KB | MIT |
| 8.2.0-canary-4 | 4 years ago | 101 KB | MIT |
| 8.2.0-canary-2 | 4 years ago | 101 KB | MIT |
| 8.1.0 | 6 years ago | 93 KB | MIT |
| 8.0.3 | 7 years ago | 90 KB | MIT |
| 8.0.2 | 8 years ago | 90 KB | MIT |
| 8.0.1 | 9 years ago | — | MIT |
| 8.0.0 | 9 years ago | — | MIT |
| 7.3.1 | 9 years ago | — | MIT |
| 7.3.0 | 9 years ago | — | MIT |
| 7.2.0 | 9 years ago | — | MIT |
| 7.1.1 | 10 years ago | — | MIT |
| 7.1.0 | 10 years ago | — | MIT |
Overview
promise is an npm package that bare bones Promises/A+ implementation. It has 5 known dependents in the graph. The latest version is 8.3.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need bare bones Promises/A+ implementation 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).
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 promise?
No — promise should not be adopted for new projects. Last published 1415 days ago.
How do I install promise?
Run `npm install promise` to add promise to your npm project.
How many dependencies does promise have?
promise declares 7 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 107 KB on disk.
What license is promise released under?
promise is distributed under the MIT license.
How popular is promise?
npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on promise.
Is promise still maintained?
The most recent release of promise (v8.3.0) was published 3 years ago.
Does promise run install scripts?
No. promise does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.