pg-boss - npm Package Compare versions

Comparing version 0.3.3 to 0.3.4

lib/manager.js

@@ -192,2 +192,5 @@ 'use strict';
                             data = args[1];
+
+                            assert(typeof data != 'function', 'publish() cannot accept a function as the payload.  Did you intend to use subscribe()?');
+
                             options = args[2];
@@ -207,4 +210,6 @@ } else if (_typeof(args[0]) == 'object') {
 
+                        options = options || {};
+
                         assert(name, 'boss requires all jobs to have a name');
-                        options = options || {};
+                        assert((typeof options === 'undefined' ? 'undefined' : _typeof(options)) == 'object', 'options should be an object');
                     } catch (error) {
@@ -211,0 +216,0 @@ return reject(error);

package.json

 {
   "name": "pg-boss",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Queueing jobs in Node.js using PostgreSQL like a boss",
@@ -5,0 +5,0 @@ "main": "./lib/index.js",

README.md

@@ -33,3 +33,5 @@ Queueing jobs in Node.js using PostgreSQL like a boss.
 
-Why would you consider using this queue over others?  Well, I will say this is a crowded space in npm, and I haven't personally used very many of them, but if you're already using Node and Postgres, you could avoid a conversation with Ops. I wrote this to remove a dependency on Redis (via the kue package), consolidating systems I have to support in production and well as upgrading to guaranteed message processing. This will likely cater to anyone already familiar with the simplicity of relational database semantics and operations (querying and backups, for example) as well as a low budget solution to a very common problem. 
+Why would you consider using this queue over others? pg-boss was created to leverage recent additions in PostreSQL 9.5
+(specifically [SKIP LOCKED](http://blog.2ndquadrant.com/what-is-select-skip-locked-for-in-postgresql-9-5) and upserts)
+which significantly enhances it's ability to act as a reliable, distributed message queue. I wrote this to remove a dependency on Redis (via the kue package), consolidating systems I have to support in production and well as upgrading to guaranteed message processing. This will likely cater to anyone already familiar with the simplicity of relational database semantics and operations (querying and backups, for example) as well as a low budget solution to a very common problem. 
 
@@ -56,9 +58,1 @@ ##Features
 * [Configuration](https://github.com/timgit/pg-boss/wiki/configuration)
-
-##Background
-pg-boss was created to leverage recent additions in PostreSQL 9.5
-(specifically [SKIP LOCKED](http://blog.2ndquadrant.com/what-is-select-skip-locked-for-in-postgresql-9-5) and upserts)
-which significantly enhances it's ability to act as a reliable, distributed message queue.
-For example, I have a performance test which regularly completes 1000 jobs per second
-([a bit longer in CI of course](https://travis-ci.org/timgit/pg-boss/jobs/127713018#L301)) once SKIP LOCKED was added
-to my job fetch CTE.

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

Lines of code

706

increased by0.28%

Worsened metrics

Total package byte prevSize

45169

decreased by-0.21%

Number of lines in readme file

57

decreased by-9.52%

No dependency changes