Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Design, build, and publish (to npm or a local/verdaccio registry) a reusable package that offloads a CPU-bound task (hashing, parsing, number crunching) to a worker_threads Worker so it never blocks the caller's event loop. Ship it correctly: a package.json exports map serving both ESM and CommonJS consumers, emitted type declarations, a files allowlist, semantic versioning, and tests that prove both the behavior and that the main thread stays responsive under load.
CPU work runs in a worker_threads Worker via message passing; the main event loop stays responsive under load (demonstrated).
exports map serves both import and require; type declarations emitted; a files allowlist limits what's published.
Semantic versioning applied; the publish flow works against a registry; no dev junk shipped.
Behavior tested; responsiveness-under-load verified; misuse handled.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Publish a dual ESM/CJS package with a worker-thread offload ## Goal Design, build, and publish (to npm or a local/verdaccio registry) a reusable package that offloads a CPU-bound task (hashing, parsing, number crunching) to a worker_threads Worker so it never blocks the caller's event loop. Ship it correctly: a package.json exports map serving both ESM and CommonJS consumers, emitted type declarations, a files allowlist, semantic versioning, and tests that prove both the behavior and that the main thread stays responsive under load. ## Acceptance criteria - [ ] Worker offload: CPU work runs in a worker_threads Worker via message passing; the main event loop stays responsive under load (demonstrated). - [ ] Dual ESM/CJS packaging: exports map serves both import and require; type declarations emitted; a files allowlist limits what's published. - [ ] Versioning & publish: Semantic versioning applied; the publish flow works against a registry; no dev junk shipped. - [ ] Tests: Behavior tested; responsiveness-under-load verified; misuse handled. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.