Files
pezkuwi-dev/packages/dev-test
Satoshi Qazi Muhammed 13a6acf80d dev-test: JSDOM's WebSocket in the browser environment
The browser environment replaces Node's Event with JSDOM's. Node's WebSocket
dispatches through Node's EventTarget, which rejects that Event, so no open,
message or error reached a listener and no connection ever came up: an
ApiPromise against a live node never became ready. JSDOM's WebSocket now
replaces Node's, as Event and CustomEvent already do. A spec completes a
handshake with a local server and receives a frame.
2026-10-11 06:06:19 +04:00
..

@pezkuwi/dev-test

This is a very basic Jest-compatible environment that could be used alongside tests. The need for this came from replacing Jest with node --test without rewriting all assertions.

It provides the following -

  1. Browser window, document, navigator (see usage for browser-specific path)
  2. jest functions, specifically spyOn (not comprehensive, some will error, some witll noop)
  3. expect functions (not comprehensive, caters for specific pezkuwi-js usage)

Usage

On thing to note is that node:test is still rapidly evolving - this includes the APIs and features. As such this requires at least Node 18.14, however 18.15+ is recommended.

The entry points are different based on the environment you would like to operate in. For a browser-like environment,

node --require @pezkuwi/dev-test/browser ...

or for a basic describe/expect/jest-only global environment

node --require @pezkuwi/dev-test/node ...

The ... above indicates any additional Node options, for instance a full command could be -

node --require @pezkuwi/dev-test/node --test something.test.js