@pryv/monitor 1.0.2 → 1.0.6

package/README.md

@@ -122,19 +122,19 @@ new Pryv.Monitor.UpdateMethod.EventsTimer({ms})
 ```
 
 This will call `monitor.updateEvents()` regularly at a rate `{ms}` in milliseconds (It has no real world but for demonstrative purposes).
-  
+
 - **Socket**
 
 ```javascript
 new Pryv.Monitor.UpdateMethod.Socket()
 ```
-  
+
 Based on websockets, it uses [lib-js-socket.io](https://github.com/pryv/lib-js-socket.io) to relay notification from Pryv.io to the monitor.
-  
+
 - **Custom**
 
 You can design your own UpdateMethod by extending the [UpdateMethod](https://github.com/pryv/lib-js-monitor/blob/master/src/UpdateMethod/UpdateMethod.js) class.
-  
+
 #### Stop monitoring
 
 ```javascript
@@ -181,10 +181,12 @@ Chain (async) `.start()`
 
 #### Node.js
 
+Install packages: `npm install pryv @pryv/socket.io @pryv/monitor`
+
 ```javascript
 const Pryv = require('pryv');
 require('@pryv/socket.io')(Pryv);
-require('../src/')(Pryv);
+require('@pryv/monitor')(Pryv);
 
 const apiEndpoint = 'https://ck60yn9yv00011hd3vu1ocpi7@jslibtest.pryv.me';
 (async () => { 
@@ -201,6 +203,10 @@ const apiEndpoint = 'https://ck60yn9yv00011hd3vu1ocpi7@jslibtest.pryv.me';
 <script src="https://api.pryv.com/lib-js/pryv.js"></script>
 <script src="https://api.pryv.com/lib-js-socket.io/pryv-socket.io.js"></script>
 <script src="https://api.pryv.com/lib-js-monitor/pryv-monitor.js"></script>
+<!-- 
+Previous lines can be replaced by a single "bundle"
+<script src="https://api.pryv.com/lib-js/pryv-socket.io-monitor.js"></script>
+-->
 
 <script>
 const apiEndpoint = 'https://ck60yn9yv00011hd3vu1ocpi7@jslibtest.pryv.me';
@@ -233,4 +239,4 @@ It can be tested on [http://pryv.github.io/lib-js-monitor](http://pryv.github.io
 
 ## Known limitations
 
-- If an event's update makes it "out of eventsGetScope". For example an (in eventsGetScope) event streamIds[] property is "moved" to a streamId not convered by the eventsGetScope, the current Pryv.io API does not provide the necessary synchronization mechanism to detect such changes.
+- If an event's update makes it "out of eventsGetScope". For example an (in eventsGetScope) event streamIds[] property is "moved" to a streamId not convered by the eventsGetScope, the current Pryv.io API does not provide the necessary synchronization mechanism to detect such changes.

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@pryv/monitor",
-  "version": "1.0.2",
+  "version": "1.0.6",
   "description": "Extends `pryv` lib-js with event driven notifications for changes on a Pryv.io account.",
   "main": "src/index.js",
   "scripts": {
     "test": "mocha --reporter spec  test/*.test.js",
     "setup": "./scripts/setup-environment-dev.sh",
+    "example": "npx rec-la ./examples",
     "build": "webpack"
   },
   "repository": {
@@ -25,10 +26,10 @@
   "author": "Pryv S.A.",
   "license": "BSD-3-Clause",
   "devDependencies": {
-    "@pryv/lib-js-common": "git+https://github.com/pryv/lib-js-common.git#1.0.2",
-    "@pryv/socket.io": "^1.0.2",
-    "chai": "^4.2.0",
-    "mocha": "^8.2.1",
-    "pryv": "^2.1.2"
+    "@pryv/lib-js-common":  "github:pryv/lib-js-common#1.0.6",
+    "@pryv/socket.io": "^1.0.6",
+    "chai": "^4.3.4",
+    "mocha": "^9.1.3",
+    "pryv": "^2.1.9"
   }
 }