Configurable number of PhantomJS instances from the includer's package.j... #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...son
After this commit, one who depends on attester in his "scripts" part of
package.json
, can additionally put in that file the following:to specify the number of PhantomJS instances (instead of passing it via
command line), but as the added benefit, the actual user who npm install'ed
his package, could type:
to take advantage of his multi-core machine.
This setting is taken into account only if there was no
--phantomjs-instances
passed from the command line when invoking attester.