events

npmv3.3.0

Node's event emitter for all engines.

Not recommended for new projects

No — events should not be adopted for new projects. Last published 2020 days ago.

AAdoption: grade A, Excellent.
92.2M downloads per week and 2 known dependents.
FMaintenance: grade F, Failing.
Last published 2020 days ago.
AWeight: grade A, Excellent.
Zero runtime dependencies, about 81 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 events 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.

81 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: node >=0.8.x
Module format: CommonJS only
TypeScript: No bundled types
Install scripts: None

Quick start

A usage example from the events README.

javascriptFull README ↗

var EventEmitter = require('events')

var ee = new EventEmitter()
ee.on('message', function (text) {
  console.log(text)
})
ee.emit('message', 'hello world')

events 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
eventsthis page	92.2M	2	MIT	5 years ago
socket.io	18M	1	MIT	10 days ago
why-is-node-running	0	1	MIT	11 days ago
abort-controller	0	4	MIT	11 days ago
event-target-shim	0	2	MIT	11 days ago

Dependencies

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

Dev (6)

airtap ^1.0.0functions-have-names ^1.2.1has ^1.0.3has-symbols ^1.0.1isarray ^2.0.5tape ^5.0.0

Used by

Popular packages that depend on events.

webpacknpm

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.

↓ 56.4M/wk◈ 29 dependents⚖ MITTS

asapnpm

High-priority task queue for Node.js and browsers

↓ 0/wk◈ 1 dependents⚖ MIT

Relationship graph

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

events dependencies dependents

Frequently installed together

acornnpm

ECMAScript parser

↓ 254.7M/wk◈ 19 dependents⚖ MITTS

@types/estreenpm

TypeScript definitions for estree

↓ 221.1M/wk◈ 12 dependents⚖ MITTS

browserslistnpm

Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset

↓ 194.7M/wk◈ 5 dependents⚖ MITTS

lodashnpm

Lodash modular utilities.

↓ 173.7M/wk◈ 20 dependents⚖ MIT

reactnpm

React is a JavaScript library for building user interfaces.

↓ 171.6M/wk◈ 82 dependents⚖ MIT

react-domnpm

React package for working with the DOM.

↓ 161.2M/wk◈ 47 dependents⚖ MIT

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 159.4M/wk◈ 277 dependents⚖ MITTS

prettiernpm

Prettier is an opinionated code formatter

↓ 132.4M/wk◈ 158 dependents⚖ MITTS

jest-environment-nodenpm

No description provided.

↓ 54.3M/wk◈ 6 dependents⚖ MITTS

jestnpm

Delightful JavaScript Testing.

↓ 48M/wk◈ 70 dependents⚖ MITTS

chrome-trace-eventnpm

A library to create a trace of your node app per Google's Trace Event format.

↓ 0/wk◈ 1 dependents⚖ MITTS

@webassemblyjs/wasm-parsernpm

WebAssembly binary format parser

↓ 0/wk◈ 5 dependents⚖ MIT

Release history

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

Recent versions of events
Version	Published	Size	License
3.3.0latest	5 years ago	81 KB	MIT
3.2.0	6 years ago	76 KB	MIT
3.1.0	6 years ago	72 KB	MIT
3.0.0	8 years ago	70 KB	MIT
2.1.0	8 years ago	63 KB	MIT
2.0.0	8 years ago	—	MIT
1.1.1	10 years ago	—	MIT
1.1.0	11 years ago	—	MIT
1.0.2	12 years ago	—	MIT
1.0.1	12 years ago	—	MIT
1.0.0	12 years ago	—	MIT
0.5.0	14 years ago	—	MIT
0.4.0	15 years ago	—	MIT
0.3.0	15 years ago	—	MIT
0.2.0	15 years ago	—	MIT

Overview

events is an npm package that node's event emitter for all engines. It is extremely widely used, with about 92.2M downloads per week and 2 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 node's event emitter for all engines 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 (92.2M weekly downloads).
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

defunctzombie goto-bus-stop gozala

Keywords

eventDispatcher eventEmitter events listeners

Frequently asked questions

Should I use events?

No — events should not be adopted for new projects. Last published 2020 days ago.

How do I install events?

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

What license is events released under?

events is distributed under the MIT license.

How popular is events?

events has approximately 92,220,526 downloads per week and 2 known dependent packages.

Is events still maintained?

The most recent release of events (v3.3.0) was published 5 years ago.

Does events run install scripts?

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