How to Install and Uninstall node-jest-worker Package on Ubuntu 21.10 (Impish Indri)

Last updated: December 23,2024

1. Install "node-jest-worker" package

Here is a brief guide to show you how to install node-jest-worker on Ubuntu 21.10 (Impish Indri)

$ sudo apt update $ sudo apt install node-jest-worker

2. Uninstall "node-jest-worker" package

Here is a brief guide to show you how to uninstall node-jest-worker on Ubuntu 21.10 (Impish Indri):

$ sudo apt remove node-jest-worker $ sudo apt autoclean && sudo apt autoremove

3. Information about the node-jest-worker package on Ubuntu 21.10 (Impish Indri)

Package: node-jest-worker
Architecture: all
Version: 26.6.3+repack+~cs64.44.39-3
Priority: optional
Section: universe/javascript
Source: node-jest
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Javascript Maintainers
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 87
Depends: node-merge-stream, node-supports-color, node-types-node
Filename: pool/universe/n/node-jest/node-jest-worker_26.6.3+repack+~cs64.44.39-3_all.deb
Size: 18900
MD5sum: f4887bc6f0a855a92b53fab0ccd181c6
SHA1: 9151fd9c7590d0380e76ab1cb82230db805e0636
SHA256: 9a79db5cf508cde218cf55c3403e515f69d276c6453b8c62202e403454f50318
SHA512: 65bbfdc80bd1e3a34f37e71baad4fe9456cb1e9781b42252236290dda4caa48762519774df9c2ae62037fba0f70b6d5b91ad8cd792f212e5f5ce968c0027181a
Homepage: https://jestjs.io
Description-en: 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.
Description-md5: d8992d5e5577e2b8ed4f6b7275eed07e