Files
pezkuwi-dev/packages/dev-test
Satoshi Qazi Muhammed 2e3c47bbd7 run-test: pass --experimental-test-module-mocks through to node
Specs that replace a module need mock.module from node:test, which
Node only exposes behind this flag. The runner rejected unknown flags,
so there was no way to turn it on. It is now accepted and forwarded to
node like --import and --require.

The repo's own test run enables it, and a spec checks that a module
registered as a mock is what a later dynamic import receives.
2026-10-10 08:42:29 +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