bree - npm Package Compare versions

Comparing version 1.1.14 to 1.1.15

package.json

		{
		"name": "bree",
		"description": "The best job scheduler for Node.js with support for cron, dates, ms, later, and human-friendly strings. Uses workers to spawn sandboxed processes, and supports async/await, retries, throttling, concurrency, and cancelable promises (graceful shutdown). Simple, fast, and the most lightweight tool for the job. Made for Forward Email and Lad.",
		"version": "1.1.14",
		"version": "1.1.15",
		"author": "Nick Baugh <niftylettuce@gmail.com> (http://niftylettuce.com/)",
		@@ -6,0 +6,0 @@ "ava": {

README.md

		@@ -567,3 +567,3 @@ <h1 align="center">

		If a job is already running, a new worker thread will not be spawned, instead an error will be thrown. This is to prevent bad practices from being used. If you need something to be run more than one time, then make the job itself run the task multiple times. This approach gives you more fine-grained control.
		If a job is already running, a new worker thread will not be spawned, instead `logger.error` will be invoked with an error message (no error will be thrown, don't worry). This is to prevent bad practices from being used. If you need something to be run more than one time, then make the job itself run the task multiple times. This approach gives you more fine-grained control.

		@@ -570,0 +570,0 @@ By default, workers run indefinitely and are not closed until they exit (e.g. via `process.exit(0)` or `process.exit(1)`, OR send to the parent port a "close" message, which will subsequently call `worker.close()` to close the worker thread.

New alerts