Unit · 16
Exports, empty state, fluent returns, validation, and list shape.
See every Unit case →Testing
131 unique checks live in one host-neutral registry. Node and Chrome execute that same inventory instead of maintaining divergent test copies.
Exports, empty state, fluent returns, validation, and list shape.
See every Unit case →Registration, typed and wildcard dispatch, once, removal, reset, and chaining.
See every Functional case →Subclassing, routing, namespaces, lifecycle composition, errors, and async peers.
See every Integration case →Given/When/Then consumer workflows, routing boundaries, lifecycle teardown, failures, and async effects.
See every Behavioral scenario →Live mutation, reentrancy, one-shot records, snapshots, prototype-like names, and throws.
See every Regression case →Playground parsing, safe display, bounded logs, benchmark evidence, units, and chart scaling.
See every Interface case →Node 22.12 and 24 run on Ubuntu, macOS, and Windows. The packed Node 22.12 floor also proves ESM import and CommonJS require load the same class.
Google Chrome Stable resolves the bare package through an import map, executes the shared ESM suite, and produces independent native V8 coverage.
Fresh projects install the tarball and prove Node ESM/CommonJS, native normal/scoped maps, and a Rollup bundle under poisoned dependency conflicts.
An installed native ESM app puts this map before the first module script and serves the files over HTTP(S):
<script type="importmap">
{"imports":{"event-pubsub":"./node_modules/event-pubsub/index.js","strong-type":"./node_modules/strong-type/index.js"}}
</script>If the app uses a strict CSP, authorize the inline import-map script with an allowed nonce or hash.