How to Install and Uninstall node-jest-worker Package on Kali Linux

Last updated: May 18,2024

1. Install "node-jest-worker" package

Please follow the guidelines below to install node-jest-worker on Kali Linux

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

2. Uninstall "node-jest-worker" package

This tutorial shows how to uninstall node-jest-worker on Kali Linux:

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

3. Information about the node-jest-worker package on Kali Linux

Package: node-jest-worker
Source: node-jest
Version: 29.6.2~ds1+~cs73.45.28-5
Installed-Size: 323
Maintainer: Debian Javascript Maintainers
Architecture: all
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)
Depends: node-chalk, node-ci-info, node-graceful-fs, node-merge-stream, node-picomatch, node-supports-color, node-types-node
Breaks: jest (<< 29.1.2~ds1+~cs70.47.21-1~), node-rollup-plugin-terser (<< 7.0.2-6~)
Size: 116416
SHA256: 3b7a7d0e4548cdc8710c30c3504f78e93603eda1188fb5ed9661f88d5b253586
SHA1: 1f483553610b138a542acbe19ca29b22dfe7a88b
MD5sum: 4c5124640aec77fa4e2eef1cd4e87d16
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.
Description-md5:
Multi-Arch: foreign
Homepage: https://jestjs.io
Section: javascript
Priority: optional
Filename: pool/main/n/node-jest/node-jest-worker_29.6.2~ds1+~cs73.45.28-5_all.deb