lie

npmv3.3.0TypeScript

A basic but performant promise implementation

Not recommended for new projects

No — lie should not be adopted for new projects. Last published 3109 days ago.

?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
FMaintenance: grade F, Failing.
Last published 3109 days ago.
AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 78 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 lie to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

78 KB

Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing lie, not just its own. Check this before a legal review, not after.

Compatibility

Node.js: No constraint declared
Module format: CommonJS only
TypeScript: Types included
Install scripts: None

Quick start

A usage example from the lie README.

javascriptFull README ↗

var Promise = require('lie');
// or use the pollyfill
require('lie/polyfill');

lie 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
liethis page	0	1	MIT	8 years ago
p-limit	293.1M	5	MIT	1 day ago
p-locate	216.9M	1	MIT	1 day ago
cross-fetch	32.9M	2	MIT	1 day ago
await-lock	0	1	MIT	1 day ago
until-async	0	1	MIT	1 day ago

Dependencies

Declared by lie v3.3.0. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

immediate ~3.0.5

Dev (18)

browserify ^13.0.0browserify-transform-cli ^1.1.1bundle-collapser ^1.2.1copyfiles ^1.0.0derequire ^1.2.0es3ify ^0.2.2inline-process-browser ^1.0.0istanbul ^0.2.6jshint ^2.4.4mkdirp ^0.5.1mocha ^1.18.0mocha-phantomjs ~3.5.0phantomjs ^1.9.9promises-aplus-tests github:calvinmetcalf/promises-tests#phantomrimraf ^2.5.4typescript ^2.7.1uglify-js ^2.4.13unreachable-branch-transform ^0.3.0

Used by

Popular packages that depend on lie.

jszipnpm

Create, read and edit .zip files with JavaScript http://stuartk.com/jszip

↓ 0/wk◈ 2 dependents⚖ (MIT OR GPL-3.0-or-later)TS

Relationship graph

Dependencies (left) and dependents (right) of lie.

lie dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS

pakonpm

zlib port to javascript - fast, modularized, with browser support

↓ 100.8M/wk◈ 2 dependents⚖ (MIT AND Zlib)TS

setimmediatenpm

A shim for the setImmediate efficient script yielding API

↓ 50.7M/wk◈ 2 dependents⚖ MIT

playwrightnpm

A high-level API to automate web browsers

↓ 0/wk◈ 18 dependents⚖ Apache-2.0TS

Release history

No releases in the last two years, typically about 36 days apart.

Recent versions of lie
Version	Published	Size	License
3.3.0latest	8 years ago	58 KB	MIT
3.2.0	8 years ago	—	MIT
3.1.1	9 years ago	—	MIT
3.1.0	10 years ago	—	MIT
3.0.4	10 years ago	—	MIT
3.0.3	10 years ago	—	MIT
3.0.2	10 years ago	—	MIT
3.0.1	11 years ago	—	MIT
3.0.0	11 years ago	—	MIT
2.9.1	11 years ago	—	MIT
2.9.0	11 years ago	—	MIT
2.8.1	11 years ago	—	MIT
2.8.0	12 years ago	—	MIT
2.7.7	12 years ago	—	MIT
2.7.6	12 years ago	—	MIT

Overview

lie is an npm package that a basic but performant promise implementation. It has 1 known dependents in the graph. The latest version is 3.3.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need a basic but performant promise implementation and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.

Pros

Ships TypeScript type definitions.
Clear open-source license (MIT).

Cons

Large dependency tree (19 direct dependencies) increases install size and audit surface.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

cwmma

Keywords

aplus async lie promise

Frequently asked questions

Should I use lie?

No — lie should not be adopted for new projects. Last published 3109 days ago.

How do I install lie?

Run `npm install lie` to add lie to your npm project.

How many dependencies does lie have?

lie declares 19 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 78 KB on disk.

What license is lie released under?

lie is distributed under the MIT license.

How popular is lie?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on lie.

Is lie still maintained?

The most recent release of lie (v3.3.0) was published 8 years ago.

Does lie run install scripts?

No. lie does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.