@achrinza/event-pubsub 5.0.5

Super light and fast Extensible ES6+ events and EventEmitters for Node and the browser. Easy for any developer level, use the same exact code in node and the browser. No frills, just high speed events!

@achrinza/event-pubsub@5.0.5 was published on 2022-03-25. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is 13 || 14 || 16 || 17.

Deprecated: This version contains transitive nested dependencies managed by @/riaevangelist. Use v5.0.6 instead. See https://github.com/achrinza/event-pubsub/issues/6 for more information.

All @achrinza/event-pubsub versions · Permanent reference to 5.0.5 · Latest release

Package specifications

Version5.0.5
License declarationMIT
Published2022-03-25T09:11:54.535Z
Node.js requirement13 || 14 || 16 || 17
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size16.00 KiB
Published file count5
Package typemodule
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars0
Repository forks2

Install @achrinza/event-pubsub 5.0.5

npm install @achrinza/event-pubsub@5.0.5
pnpm add @achrinza/event-pubsub@5.0.5
yarn add @achrinza/event-pubsub@5.0.5

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness