mongo-watch - npm Package Compare versions

Comparing version 0.0.6 to 0.0.7

package.json

 {
   "name":"mongo-watch",
   "description":"A mongo watcher.  This ties into the MongoDB replication oplog, and exposes all data modifications via an EventEmitter.",
-  "version":"0.0.6",
+  "version":"0.0.7",
   "homepage":"http://github.com/TorchlightSoftware/mongo-watcher",
@@ -6,0 +6,0 @@ "repository":"git://github.com/TorchlightSoftware/mongo-watcher.git",

README.md

@@ -8,3 +8,3 @@ # Mongo Watcher
 1. Have access to the oplog.  This will not be available on shared DB hosting, as it would reveal everyone else's database transactions to you.
-2. Have replication enabled.  This can be done by starting mongod with the option '--replSet someArbitraryName'
+2. Have replication enabled.  This can be done by starting mongod with the option '--replSet someArbitraryName'.  You must then call `rs.initiate()` from the mongo CLI.
 
@@ -30,3 +30,3 @@ The watcher is fairly low latency and overhead.  On my machine a test with a single insert and watcher takes 20ms.  The cursor used to tail the oplog is being initialized with {awaitdata: true} so the data should be getting pushed from MongoDB's internal mechanism, instead of polling.
 
-watcher = new MongoWatch {parser: 'pretty'}
+watcher = new MongoWatch {format: 'pretty'}
 
@@ -33,0 +33,0 @@ # watch the collection

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

18665

increased by18.94%

Number of package files

13

increased by8.33%

No dependency changes