{
  "manifest": {
    "name": "jest-worker",
    "version": "26.6.2",
    "repository": {
      "type": "git",
      "url": "https://github.com/facebook/jest.git",
      "directory": "packages/jest-worker"
    },
    "license": "MIT",
    "main": "build/index.js",
    "types": "build/index.d.ts",
    "dependencies": {
      "@types/node": "*",
      "merge-stream": "^2.0.0",
      "supports-color": "^7.0.0"
    },
    "devDependencies": {
      "@types/merge-stream": "^1.1.2",
      "@types/supports-color": "^7.2.0",
      "get-stream": "^6.0.0",
      "worker-farm": "^1.6.0"
    },
    "engines": {
      "node": ">= 10.13.0"
    },
    "publishConfig": {
      "access": "public"
    },
    "gitHead": "4c46930615602cbf983fb7e8e82884c282a624d5",
    "_registry": "npm",
    "_loc": "/homez.1033/heliovt/.cache/yarn/v6/npm-jest-worker-26.6.2-7f72cbc4d643c365e27b9fd775f9d0eaa9c7a8ed-integrity/node_modules/jest-worker/package.json",
    "readmeFilename": "README.md",
    "readme": "# jest-worker\n\nModule for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.\n\nThe 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.\n\nThe 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.\n\nThe list of exposed methods can be explicitly provided via the `exposedMethods` option. If it is not provided, it will be obtained by requiring the child module into the main process, and analyzed via reflection. Check the \"minimal example\" section for a valid one.\n\n## Install\n\n```sh\n$ yarn add jest-worker\n```\n\n## Example\n\nThis example covers the minimal usage:\n\n### File `parent.js`\n\n```javascript\nimport JestWorker from 'jest-worker';\n\nasync function main() {\n  const worker = new JestWorker(require.resolve('./Worker'));\n  const result = await worker.hello('Alice'); // \"Hello, Alice\"\n}\n\nmain();\n```\n\n### File `worker.js`\n\n```javascript\nexport function hello(param) {\n  return 'Hello, ' + param;\n}\n```\n\n## Experimental worker\n\nNode 10 shipped with [worker-threads](https://nodejs.org/api/worker_threads.html), a \"threading API\" that uses SharedArrayBuffers to communicate between the main process and its child threads. This experimental Node feature can significantly improve the communication time between parent and child processes in `jest-worker`.\n\nSince `worker_threads` are considered experimental in Node, you have to opt-in to this behavior by passing `enableWorkerThreads: true` when instantiating the worker. While the feature was unflagged in Node 11.7.0, you'll need to run the Node process with the `--experimental-worker` flag for Node 10.\n\n## API\n\nThe only exposed method is a constructor (`JestWorker`) that is initialized by passing the worker path, plus an options object.\n\n### `workerPath: string` (required)\n\nNode module name or absolute path of the file to be loaded in the child processes. Use `require.resolve` to transform a relative path into an absolute one.\n\n### `options: Object` (optional)\n\n#### `exposedMethods: $ReadOnlyArray<string>` (optional)\n\nList of method names that can be called on the child processes from the parent process. You cannot expose any method named like a public `Worker` method, or starting with `_`. If you use method auto-discovery, then these methods will not be exposed, even if they exist.\n\n#### `numWorkers: number` (optional)\n\nAmount of workers to spawn. Defaults to the number of CPUs minus 1.\n\n#### `maxRetries: number` (optional)\n\nMaximum amount of times that a dead child can be re-spawned, per call. Defaults to `3`, pass `Infinity` to allow endless retries.\n\n#### `forkOptions: Object` (optional)\n\nAllow customizing all options passed to `childProcess.fork`. By default, some values are set (`cwd`, `env` and `execArgv`), but you can override them and customize the rest. For a list of valid values, check [the Node documentation](https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options).\n\n#### `computeWorkerKey: (method: string, ...args: Array<any>) => ?string` (optional)\n\nEvery time a method exposed via the API is called, `computeWorkerKey` is also called in order to bound the call to a worker. This is useful for workers that are able to cache the result or part of it. You bound calls to a worker by making `computeWorkerKey` return the same identifier for all different calls. If you do not want to bind the call to any worker, return `null`.\n\nThe callback you provide is called with the method name, plus all the rest of the arguments of the call. Thus, you have full control to decide what to return. Check a practical example on bound workers under the \"bound worker usage\" section.\n\nBy default, no process is bound to any worker.\n\n#### `setupArgs: Array<mixed>` (optional)\n\nThe arguments that will be passed to the `setup` method during initialization.\n\n#### `WorkerPool: (workerPath: string, options?: WorkerPoolOptions) => WorkerPoolInterface` (optional)\n\nProvide a custom worker pool to be used for spawning child processes. By default, Jest will use a node thread pool if available and fall back to child process threads.\n\n#### `enableWorkerThreads: boolean` (optional)\n\n`jest-worker` will automatically detect if `worker_threads` are available, but will not use them unless passed `enableWorkerThreads: true`.\n\n## JestWorker\n\n### Methods\n\nThe returned `JestWorker` instance has all the exposed methods, plus some additional ones to interact with the workers itself:\n\n#### `getStdout(): Readable`\n\nReturns a `ReadableStream` where the standard output of all workers is piped. Note that the `silent` option of the child workers must be set to `true` to make it work. This is the default set by `jest-worker`, but keep it in mind when overriding options through `forkOptions`.\n\n#### `getStderr(): Readable`\n\nReturns a `ReadableStream` where the standard error of all workers is piped. Note that the `silent` option of the child workers must be set to `true` to make it work. This is the default set by `jest-worker`, but keep it in mind when overriding options through `forkOptions`.\n\n#### `end()`\n\nFinishes the workers by killing all workers. No further calls can be done to the `Worker` instance.\n\nReturns a Promise that resolves with `{ forceExited: boolean }` once all workers are dead. If `forceExited` is `true`, at least one of the workers did not exit gracefully, which likely happened because it executed a leaky task that left handles open. This should be avoided, force exiting workers is a last resort to prevent creating lots of orphans.\n\n**Note:**\n\n`await`ing the `end()` Promise immediately after the workers are no longer needed before proceeding to do other useful things in your program may not be a good idea. If workers have to be force exited, `jest-worker` may go through multiple stages of force exiting (e.g. SIGTERM, later SIGKILL) and give the worker overall around 1 second time to exit on its own. During this time, your program will wait, even though it may not be necessary that all workers are dead before continuing execution.\n\nConsider deliberately leaving this Promise floating (unhandled resolution). After your program has done the rest of its work and is about to exit, the Node process will wait for the Promise to resolve after all workers are dead as the last event loop task. That way you parallelized computation time of your program and waiting time and you didn't delay the outputs of your program unnecessarily.\n\n### Worker IDs\n\nEach worker has a unique id (index that starts with `1`), which is available inside the worker as `process.env.JEST_WORKER_ID`.\n\n## Setting up and tearing down the child process\n\nThe child process can define two special methods (both of them can be asynchronous):\n\n- `setup()`: If defined, it's executed before the first call to any method in the child.\n- `teardown()`: If defined, it's executed when the farm ends.\n\n# More examples\n\n## Standard usage\n\nThis example covers the standard usage:\n\n### File `parent.js`\n\n```javascript\nimport JestWorker from 'jest-worker';\n\nasync function main() {\n  const myWorker = new JestWorker(require.resolve('./Worker'), {\n    exposedMethods: ['foo', 'bar', 'getWorkerId'],\n    numWorkers: 4,\n  });\n\n  console.log(await myWorker.foo('Alice')); // \"Hello from foo: Alice\"\n  console.log(await myWorker.bar('Bob')); // \"Hello from bar: Bob\"\n  console.log(await myWorker.getWorkerId()); // \"3\" -> this message has sent from the 3rd worker\n\n  const {forceExited} = await myWorker.end();\n  if (forceExited) {\n    console.error('Workers failed to exit gracefully');\n  }\n}\n\nmain();\n```\n\n### File `worker.js`\n\n```javascript\nexport function foo(param) {\n  return 'Hello from foo: ' + param;\n}\n\nexport function bar(param) {\n  return 'Hello from bar: ' + param;\n}\n\nexport function getWorkerId() {\n  return process.env.JEST_WORKER_ID;\n}\n```\n\n## Bound worker usage:\n\nThis example covers the usage with a `computeWorkerKey` method:\n\n### File `parent.js`\n\n```javascript\nimport JestWorker from 'jest-worker';\n\nasync function main() {\n  const myWorker = new JestWorker(require.resolve('./Worker'), {\n    computeWorkerKey: (method, filename) => filename,\n  });\n\n  // Transform the given file, within the first available worker.\n  console.log(await myWorker.transform('/tmp/foo.js'));\n\n  // Wait a bit.\n  await sleep(10000);\n\n  // Transform the same file again. Will immediately return because the\n  // transformed file is cached in the worker, and `computeWorkerKey` ensures\n  // the same worker that processed the file the first time will process it now.\n  console.log(await myWorker.transform('/tmp/foo.js'));\n\n  const {forceExited} = await myWorker.end();\n  if (forceExited) {\n    console.error('Workers failed to exit gracefully');\n  }\n}\n\nmain();\n```\n\n### File `worker.js`\n\n```javascript\nimport babel from '@babel/core';\n\nconst cache = Object.create(null);\n\nexport function transform(filename) {\n  if (cache[filename]) {\n    return cache[filename];\n  }\n\n  // jest-worker can handle both immediate results and thenables. If a\n  // thenable is returned, it will be await'ed until it resolves.\n  return babel.transformFileAsync(filename).then(result => {\n    cache[filename] = result;\n\n    return result;\n  });\n}\n```\n",
    "description": "Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.",
    "licenseText": "MIT License\n\nCopyright (c) Facebook, Inc. and its affiliates.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n"
  },
  "artifacts": [],
  "remote": {
    "resolved": "https://registry.yarnpkg.com/jest-worker/-/jest-worker-26.6.2.tgz#7f72cbc4d643c365e27b9fd775f9d0eaa9c7a8ed",
    "type": "tarball",
    "reference": "https://registry.yarnpkg.com/jest-worker/-/jest-worker-26.6.2.tgz",
    "hash": "7f72cbc4d643c365e27b9fd775f9d0eaa9c7a8ed",
    "integrity": "sha512-KWYVV1c4i+jbMpaBC+U++4Va0cp8OisU185o73T1vo99hqi7w8tSJfUXYswwqqrjzwxa6KpRK54WhPvwf5w6PQ==",
    "registry": "npm",
    "packageName": "jest-worker",
    "cacheIntegrity": "sha512-KWYVV1c4i+jbMpaBC+U++4Va0cp8OisU185o73T1vo99hqi7w8tSJfUXYswwqqrjzwxa6KpRK54WhPvwf5w6PQ== sha1-f3LLxNZDw2Xie5/XdfnQ6qnHqO0="
  },
  "registry": "npm",
  "hash": "7f72cbc4d643c365e27b9fd775f9d0eaa9c7a8ed"
}