immediate

npmv3.3.0

A cross browser microtask library

Not recommended for new projects

No — immediate should not be adopted for new projects. Last published 2283 days ago.

?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
FMaintenance: grade F, Failing.
Last published 2283 days ago.
AWeight: grade A, Excellent.
Zero runtime dependencies, about 20 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 immediate 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.

20 KB

Install size

Unpacked size of this package plus its entire runtime tree.

—

Tree depth

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 immediate README.

jsFull README ↗

var immediate = require("immediate");

immediate(function () {
  // this will run soon
});

immediate(function (arg1, arg2) {
  // get your args like in iojs
}, thing1, thing2);

Dependencies

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

Dev (6)

browserify ^16.5.1derequire ^2.1.1jshint ^2.5.1tap-spec ^5.0.0tape ^4.0.0uglify-js ^2.4.13

Used by

Popular packages that depend on immediate.

lienpm

A basic but performant promise implementation

↓ 0/wk◈ 1 dependents⚖ MITTS

Relationship graph

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

immediate dependencies dependents

Release history

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

Recent versions of immediate
Version	Published	Size	License
3.3.0latest	6 years ago	20 KB	MIT
3.2.3	10 years ago	—	MIT
3.0.6	10 years ago	—	MIT
3.2.2	11 years ago	—	MIT
3.0.5	11 years ago	—	MIT
3.2.1	11 years ago	—	MIT
3.0.4	11 years ago	—	MIT
3.2.0	11 years ago	—	MIT
3.1.0	11 years ago	—	MIT
3.0.3	12 years ago	—	MIT
3.0.2	12 years ago	—	MIT
3.0.1	12 years ago	—	MIT
3.0.0	12 years ago	—	MIT
2.7.2	12 years ago	—	MIT
2.7.1	12 years ago	—	MIT

Overview

immediate is an npm package that a cross browser microtask library. 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 cross browser microtask library 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.

Maintainers

cwmma

Frequently asked questions

Should I use immediate?

No — immediate should not be adopted for new projects. Last published 2283 days ago.

How do I install immediate?

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

What license is immediate released under?

immediate is distributed under the MIT license.

How popular is immediate?

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

Is immediate still maintained?

The most recent release of immediate (v3.3.0) was published 6 years ago.

Does immediate run install scripts?

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