mirror of
https://github.com/pezkuwichain/pezkuwi-dev.git
synced 2026-10-22 03:36:18 +00:00
With the manifests broken,b65f265and4539abbworked around the symptoms: rootJs imported itself by relative path instead of as @pezkuwi/dev, a hand-written dynamic.d.mts stood in for the .mjs, and suite.spec.ts declared its own describe/it/expect and imported a .d.ts at run time, which failed the file. All three are reverted to upstream's form. The import-attribute check now expects `with`: Node 22 removed `assert`. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@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 -
- Browser
window,document,navigator(see usage for browser-specific path) jestfunctions, specificallyspyOn(not comprehensive, some will error, some witll noop)expectfunctions (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