batch-cluster
Advanced tools
batch-cluster - npm Package Versions
Changelog
v5.1.0
- ✨
ChildProcessFactorysupports thunks that return either aChildProcessorPromise<ChildProcess> - 📦 Update deps
Changelog
v5.0.0
- 💔 The
rejectTaskOnStderrAPI, which was added in v4.1.0 and applied to all tasks for a givenBatchClusterinstance, proved to be a poor decision, and has been removed. TheParserAPI, which is task-specific, now receives both stdin and stderr streams. Parsers then have the necessary context to decide what to do on a per task or per task-type basis. - 🐞 In previous versions, batch processes were recycled if any task had any type of error. This version allows pids to live even if they emit data to stderr.
Changelog
v4.3.0
- ✨ If your tasks return interim progress and you want to capture that data
as it happens, BatchCluster now emits
taskDataevents with the data and the current task (which may be undefined) as soon as the stream data is emitted. - 📦 Pulled in latest dependency versions
Changelog
v4.2.0
- 📦 In the interests of less noise, the default logger is now the
NoLogger. Consumers may use theConsoleLoggeror anotherLoggerimplementation as they see fit.
Changelog
v4.1.0
- ✨ Support for demoting task errors from
stderremissions:BatchProcess.rejectTaskOnStderris a per-task, per-error predicate which allows for a given error to be handled without always rejecting the task. This can be handy if the script you're wrapping (like ExifTool) writes non-fatal warnings to stderr. - ✨
BatchProcessOptions.passandBatchProcessOptions.failcan be RegExp instances now, if you have more exotic parsing needs.
Changelog
v4.0.0
-
💔 Using Node 8+ to determine if a process is running with
kill(pid, 0)turns out to be unreliable (as it returns true even after the process exits). I tried to pull in the best-maintained "process-exists" external dependency, but that pulled in 15 more modules (this used to be a zero-deps module), and it was extremely unperformant on Windows.The TL;DR: is that
running(pid)now returns aPromise<boolean>, which had far-reaching signature changes to accomodate the new asynchronicity, hence the major version bump. -
💔 In an effort to reduce this library's complexity, I'm removing retry functionality. All parameters associated to retries are now gone.
-
✨ Internal state validation is now exposed by BatchCluster, and is used by tests to ensure no internal errors happen during integration tests. Previously these errors were simply logged.
Changelog
v3.2.0
- 📦 New
Loggermethods,withLevels,withTimestamps, andfilterLevelswere shoved into a newLoggernamespace.
Changelog
v3.1.0
- ✨ Added simple timestamp and levels logger prefixer for tests
- 🐞 Errors rethrown via BatchProcess now strip extraneous
Error:prefixes - 🐞 For a couple internal errors (versionCommend startup errors and internal
state inconsistencies on
onExitthat aren't fatal), we now log.errorrather than throw Error() or ignore.
Changelog
v3.0.0
- ✨/💔
Taskpromises are only rejected withErrorinstances now. Note that also means thatBatchProcessObservertypes are more strict. It could be argued that this isn't an API breaking change as it only makes rejection values more strict, but people may need to change their error handling, so I'm bumping the major version to highlight that. Resolves #3. Thanks for the issue, Nils Knappmeier!