</>PackageGraphPackageGraph

strict-event-emitter

npmv0.5.1TypeScript

Type-safe implementation of EventEmitter for browser and Node.js

Adopt with care

strict-event-emitter is usable, with caveats. Last published 1084 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 1084 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 45 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 strict-event-emitter to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

45 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
ESM + CommonJS
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the strict-event-emitter README.

jsFull README ↗
// index.js
const emitter = new EventEmitter()

// Let's say our application expects a "ping"
// event with the number payload.
emitter.on('ping', (n: number) => {})

// We can, however, emit a different event by mistake.
emitter.emit('pong', 1)

// Or even the correct event with the wrong data.
emitter.emit('ping', 'wait, not a number')

Dependencies

Declared by strict-event-emitter v0.5.1. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (10)

@ossjs/release ^0.8.0@types/events ^3.0.0@types/jest ^29.2.4jest ^29.3.1jest-extended ^3.2.0rimraf ^3.0.2ts-jest ^29.0.3ts-node ^9.1.1tsup ^6.2.3typescript 4.8

Used by

Popular packages that depend on strict-event-emitter.

@mswjs/interceptorsnpm

Low-level network interception library for Node.js.

↓ 20.3M/wk◈ 1 dependents⚖ MITTS
mswnpm

Seamless REST/GraphQL API mocking library for browser and Node.js.

↓ 0/wk◈ 5 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of strict-event-emitter.

@mswjs/intercepto…mswstrict-event-emit…
strict-event-emitter dependencies dependents

Frequently installed together

undicinpm

An HTTP/1.1 client, written from scratch for Node.js

↓ 158.5M/wk◈ 15 dependents⚖ MITTS
axiosnpm

Promise based HTTP client for the browser and node.js

↓ 106.5M/wk◈ 4 dependents⚖ MITTS
expressnpm

Fast, unopinionated, minimalist web framework

↓ 92.8M/wk◈ 17 dependents⚖ MIT
vitestnpm

Next generation testing framework powered by Vite

↓ 92.7M/wk◈ 129 dependents⚖ MITTS
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.

↓ 49.8M/wk◈ 29 dependents⚖ MITTS
@playwright/testnpm

A high-level API to automate web browsers

↓ 0/wk◈ 9 dependents⚖ Apache-2.0TS
outvariantnpm

Type-safe implementation of invariant with positionals.

↓ 0/wk◈ 3 dependents⚖ MITTS
@open-draft/deferred-promisenpm

A Promise-compatible abstraction that defers resolving/rejecting promises to another closure.

↓ 0/wk◈ 2 dependents⚖ MIT
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
jsdomnpm

A JavaScript implementation of many web standards

↓ 0/wk◈ 20 dependents⚖ MIT
is-node-processnpm

Reliably determines if the code is running in Node.js

↓ 0/wk◈ 3 dependents⚖ MITTS
type-festnpm

A collection of essential TypeScript types

↓ 337.8M/wk◈ 6 dependents⚖ (MIT OR CC0-1.0)TS

Release history

No releases in the last two years, typically about 1 day apart.

Recent versions of strict-event-emitter
VersionPublishedSizeLicense
0.5.1latest3 years ago45 KBMIT
0.5.03 years ago43 KBMIT
0.4.63 years ago14 KBMIT
0.4.53 years ago14 KBMIT
0.4.43 years ago14 KBMIT
0.4.33 years ago14 KBMIT
0.4.23 years ago14 KBMIT
0.4.13 years ago14 KBMIT
0.4.03 years ago14 KBMIT
0.3.23 years ago19 KBMIT
0.3.13 years ago8.6 KBMIT
0.3.03 years ago8.5 KBMIT
0.2.83 years ago8.4 KBMIT
0.2.73 years ago8.4 KBMIT
0.2.63 years ago8.4 KBMIT

Overview

strict-event-emitter is an npm package that type-safe implementation of EventEmitter for browser and Node.js. It has 2 known dependents in the graph. The latest version is 0.5.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need type-safe implementation of EventEmitter for browser and Node.js and value a focused solution.

When not to use it

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

Pros

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

Cons

  • No significant drawbacks detected from available metadata.

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

Maintainers

kettanaito

Frequently asked questions

Should I use strict-event-emitter?

strict-event-emitter is usable, with caveats. Last published 1084 days ago.

How do I install strict-event-emitter?

Run `npm install strict-event-emitter` to add strict-event-emitter to your npm project.

What license is strict-event-emitter released under?

strict-event-emitter is distributed under the MIT license.

How popular is strict-event-emitter?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on strict-event-emitter.

Is strict-event-emitter still maintained?

The most recent release of strict-event-emitter (v0.5.1) was published 3 years ago.

Does strict-event-emitter run install scripts?

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