You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: extract shared DOM/testing core to @pokujs/dom + benchmark suite (#14)
* feat: extract shared DOM/testing core to @pokujs/dom, add benchmark suite with teardown-skew fix
- Move shared infrastructure (screen proxy, metrics emitter, getNow, DOM env\n setup, plugin internals) to @pokujs/dom dependency\n- All src/ modules now re-export from @pokujs/dom; react-specific logic retained\n- Add @pokujs/dom ^0.1.0 as a runtime dependency\n- Add full benchmark suite (Poku vs Jest vs Vitest, happy-dom & jsdom)\n- Fix benchmark happy-dom timing: parse Poku reported Duration from stdout\n to exclude Happy DOM async-teardown overhead from wall-clock measurements\n- benchmark/results.json and benchmark/REPORT.md included with latest results
* chore: update @pokujs/dom to ^1.0.1
* fix: use registry-resolved package-lock.json for @pokujs/dom
* chore: update benchmark report and results
* chore: bump @pokujs/dom to ^1.1.0
* fix: add deno.json import map for @pokujs/dom
Deno with isolation:none loads all test files in the same npm:poku
process. In that context bare specifiers like @pokujs/dom are not
resolved from node_modules automatically. Adding an explicit import
map entry pointing to npm:@pokujs/dom fixes resolution for all
test files that transitively import @pokujs/dom.
* chore: bump @pokujs/dom to ^1.1.1 and add multi-suite runner
* chore: bump @pokujs/dom to ^1.1.2
* chore: update package-lock.json for @pokujs/dom ^1.1.2
0 commit comments