jest-worker - npm Package Compare versions

Comparing version 21.3.0-beta.8 to 21.3.0-beta.9

build/index.js

@@ -58,2 +58,3 @@ /**
 
+
   constructor(workerPath) {let options = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {};
@@ -78,6 +79,13 @@ const numWorkers = options.numWorkers || (_os || _load_os()).default.cpus().length - 1;
       const worker = new (_worker || _load_worker()).default(workerOptions);
+      const workerStdout = worker.getStdout();
+      const workerStderr = worker.getStderr();
 
-      stdout.add(worker.getStdout());
-      stderr.add(worker.getStderr());
+      if (workerStdout) {
+        stdout.add(workerStdout);
+      }
 
+      if (workerStderr) {
+        stderr.add(workerStderr);
+      }
+
       workers[i] = worker;
@@ -121,2 +129,3 @@ }
     this._workers = workers;
+    this._offset = 0;
   }
@@ -157,2 +166,3 @@
       const workers = this._workers;
+      const length = workers.length;
       const cacheKeys = this._cacheKeys;
@@ -190,6 +200,8 @@ const request = [(_types || _load_types()).CHILD_MESSAGE_CALL, false, method, args];
       // ... otherwise use all workers, so the first one available will pick it.
-      for (let i = 0; i < workers.length; i++) {
-        workers[i].send(request, callback);
+      for (let i = 0; i < length; i++) {
+        workers[(i + this._offset) % length].send(request, callback);
       }
+
+      this._offset++;
     });
   }};

package.json

 {
   "name": "jest-worker",
-  "version": "21.3.0-beta.8",
+  "version": "21.3.0-beta.9",
   "repository": {
@@ -5,0 +5,0 @@ "type": "git",

README.md

 # jest-worker
 
-Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.
+Module for executing heavy tasks under forked processes in parallel, by
+providing 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 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.
+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.
 
-The 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.
+The 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.
 
@@ -44,10 +60,11 @@ ## Install
 
-The only exposed method is a constructor (`Worker`) that is initialized by passing the worker path, plus an options object.
+The only exposed method is a constructor (`Worker`) that is initialized by
+passing the worker path, plus an options object.
 
-
 ### `workerPath: string` (required)
 
-Node 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.
+Node 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.
 
-
 ### `options: Object` (optional)
@@ -57,3 +74,6 @@
 
-List 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.
+List 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.
 
@@ -66,35 +86,50 @@ #### `numWorkers: number` (optional)
 
-Maximum amount of times that a dead child can be re-spawned, per call. Defaults to `3`, pass `Infinity` to allow endless retries.
+Maximum amount of times that a dead child can be re-spawned, per call. Defaults
+to `3`, pass `Infinity` to allow endless retries.
 
 #### `forkOptions: Object` (optional)
 
-Allow customizing all options passed to `childProcess.fork`. By default, some values are set (`cwd` and `env`), 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).
+Allow customizing all options passed to `childProcess.fork`. By default, some
+values are set (`cwd` and `env`), 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).
 
 #### `computeWorkerKey: (method: string, ...args: Array<any>) => ?string` (optional)
 
-Every 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`.
+Every 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`.
 
-The 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.
+The 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.
 
 By default, no process is bound to any worker.
 
-
 ## Worker
 
-The returned `Worker` instance has all the exposed methods, plus some additional ones to interact with the workers itself:
+The returned `Worker` instance has all the exposed methods, plus some additional
+ones to interact with the workers itself:
 
-
 ### `getStdout(): Readable`
 
-Returns 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`.
+Returns 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`.
 
-
 ### `getStderr(): Readable`
 
-Returns 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`.
+Returns 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`.
 
-
 ### `end()`
 
-Finishes the workers by killing all workers. No further calls can be done to the `Worker` instance.
+Finishes the workers by killing all workers. No further calls can be done to the
+`Worker` instance.
 
@@ -139,3 +174,2 @@ # More examples
 
-
 ## Bound worker usage:
@@ -175,3 +209,2 @@
 ```javascript
-
 import babel from 'babel-core';
@@ -193,3 +226,3 @@
       } else {
-        resolve(cache[filename] = result);
+        resolve((cache[filename] = result));
       }
@@ -196,0 +229,0 @@ });

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

25637

increased by0.73%

Lines of code

383

increased by2.41%

Number of lines in readme file

227

increased by17.01%

Worsened metrics

Number of package files

6

decreased by-14.29%

No dependency changes