Package: node-jest-worker
Source: node-jest
Version: 29.6.2~ds7+~cs73.45.28-3
Architecture: all
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Installed-Size: 250
Depends: node-chalk, node-ci-info (>> 4.4.0+~cs8.2.0-1~), node-graceful-fs, node-merge-stream, node-picomatch, node-supports-color (>= 9.0~), node-types-node
Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~)
Replaces: jest (<< 29.1.2~ds1+~cs70.47.21-1~)
Provides: node-jest-schemas (= 29.6.0), node-jest-types (= 29.6.1), node-jest-util (= 29.6.2)
Section: javascript
Priority: optional
Multi-Arch: foreign
Homepage: https://jestjs.io
Description: Nodejs module for executing heavy tasks under forked processes in parallel
 jest-worker provides a `Promise` based interface, minimum overhead and
 bound workers.
 .
 The module works by providing an absolute path of the module to be loaded in
 all forked processes. Files relative to a node module are also accepted. All
 methods are exposed on the parent process as promises, so they can be
 `await`'ed. Child (worker) methods can either be synchronous or asynchronous.
 .
 The module also implements support for bound workers. Binding a worker means
 that, based on certain parameters, the same task will always be executed by
 the same worker. The way bound workers work is by using the returned string
 of the `computeWorkerKey` method. If the string was used before for a task,
 the call will be queued to the related worker that processed the task earlier;
 if not, it will be executed by the first available worker, then sticked to the
 worker that executed it; so the next time it will be processed by the same
 worker. If you have no preference on the worker executing the task, but you
 have defined a `computeWorkerKey` method because you want _some_ of the tasks
 to be sticked, you can return `null` from it.
