seneca-transport - npm Package Compare versions

Comparing version 2.0.0 to 2.1.0

CHANGES.md

@@ -0,1 +1,8 @@
+## 2.1.0 2016-08-25
+
+* Removed seneca-chain dependency PR#115
+* Updated dependencies
+* Added Seneca 3 and Node 6 support
+* Dropped Node 0.10, 0.12, 5 support
+
 ## 2.0.0 2016-08-12
@@ -5,3 +12,3 @@
 * Dropped support for Node 0.10, 0.12
-* Depependencies update
+* Dependencies update
 
@@ -8,0 +15,0 @@ ## 1.3.0

package.json

 {
   "name": "seneca-transport",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "description": "Seneca transport",
@@ -23,4 +23,23 @@ "main": "transport.js",
     "coveralls": "lab -s -P test -r lcov | coveralls",
-    "annotate": "docco transport.js -o doc; open doc/transport.html"
+    "annotate": "docco transport.js -o docs/annotated; open docs/annotated/transport.html"
   },
+  "contributors": [
+    "Richard Rodger (https://github.com/rjrodger)",
+    "Wyatt Preul (https://github.com/geek)",
+    "Dean McDonnell (https://github.com/mcdonnelldean)",
+    "Mihai Dima (https://github.com/mihaidma)",
+    "David Gonzalez (https://github.com/dgonzalez)",
+    "Glen Keane (https://github.com/thekemkid)",
+    "Marco Piraccini (https://github.com/marcopiraccini)",
+    "Shane Lacey (https://github.com/shanel262)",
+    "Cristian Kiss (https://github.com/ckiss)",
+    "jaamison (https://github.com/jaamison)",
+    "peterli888 (https://github.com/peterli888)",
+    "Emer Rutherford (https://github.com/eeswr)",
+    "Greg Kubisa (https://github.com/gkubisa)",
+    "Geoffrey Clements (https://github.com/baldmountain)",
+    "Rumkin (https://github.com/rumkin)",
+    "Boris Jonica (https://github.com/bjonica)",
+    "Damien Simonin Feugas (https://github.com/feugy)"
+  ],
   "dependencies": {
@@ -30,3 +49,3 @@ "eraro": "0.4.1",
     "jsonic": "0.2.2",
-    "lodash": "4.14.2",
+    "lodash": "4.15.0",
     "lru-cache": "4.0.1",
@@ -49,8 +68,18 @@ "ndjson": "1.4.3",
     "eslint-plugin-standard": "2.x.x",
-    "lab": "10.9.x",
+    "lab": "11.0.x",
     "pre-commit": "1.1.x",
     "seneca": "plugin",
-    "seneca-entity": "1.2.x",
+    "seneca-entity": "1.3.x",
     "seneca-transport-test": "0.2.0"
-  }
+  },
+  "files": [
+    "transport.js",
+    "README.md",
+    "LICENSE.txt",
+    "bench.js",
+    "lib"
+  ],
+  "pre-commit": [
+    "test"
+  ]
 }

README.md

@@ -17,5 +17,5 @@ ![Seneca](http://senecajs.org/files/assets/seneca-logo.png)
 
-seneca-transport's source can be read in an annotated fashion by,
+seneca-transport's source can be read in an annotated fashion by:
 - running `npm run annotate`
-- viewing [./doc/transport.html](./doc/transport.html) locally
+- viewing ./docs/annotated/transport.html locally
 
@@ -36,3 +36,3 @@ If you're using this module, and need help, you can:
 
-This plugin module is included in the main Seneca module,
+This plugin module is included in the main Seneca module:
 
@@ -87,6 +87,5 @@ ```sh
 
-Example with HTTPS
+Example with HTTPS:
 
-To enable HTTPS make sure to set the protocol option to 'https' and in the
-listen function set the serverOptions object with the `key` and `cert` keys.
+To enable HTTPS, pass an options object to the `listen` function setting the `protocol` option to 'https' and provide a `serverOptions` object with `key` and `cert` properties.
 
@@ -140,3 +139,3 @@ ```js
 running in server mode. You'll need to kill all the Node.js processes
-between execution runs. The quickest way to do this is:
+between execution runs. The quickest way to do this is:_
 
@@ -146,3 +145,2 @@ ```sh
 ```
-_
 
@@ -166,3 +164,3 @@
 server (which has an identifier of _ly../..80/-_). The server performs the
-action, generating the result <code>{hex=#FF0000}</code>, and sending
+action, generating the result <code>{hex=#FF0000}</code>, and sends
 it back.
@@ -191,3 +189,3 @@
 
-The next two fields show the action pattern of the message
+The next two fields show the action pattern of the message, 
 <code>color:red</code>, followed by the actual data of the request
@@ -218,3 +216,3 @@ message (when inbound), or the response message (when outbound).
 You've run this example in a single Node.js process up to now. Of
-course, the whole point is to run it a separate processes! Let's do
+course, the whole point is to run it in separate processes! Let's do
 that. First, here's the server:
@@ -461,3 +459,3 @@
 
-To communicate with a Seneca instance over TCP you can send from command line a message that Seneca understands:
+To communicate with a Seneca instance over TCP, you can send a message from the command line that Seneca understands:
 
@@ -499,18 +497,18 @@ ```sh
 you need to specify the patterns you are interested in. In Seneca,
-this is done with a _pin_.
+this is done with a `pin`.
 
-A Seneca _pin_ is a pattern for action patterns. You provide a list of
+A Seneca `pin` is a pattern for action patterns. You provide a list of
 property names and values that must match. Unlike ordinary action
-patterns, where the values are fixed, with a _pin_, you can use globs
+patterns, where the values are fixed, with a `pin`, you can use globs
 to match more than one value. For example, let's say you have the patterns:
 
-   * _foo:1,bar:zed-aaa_
-   * _foo:1,bar:zed-bbb_
-   * _foo:1,bar:zed-ccc_
+   * <code>foo:1,bar:zed-aaa</code>
+   * <code>foo:1,bar:zed-bbb</code>
+   * <code>foo:1,bar:zed-ccc</code>
 
-Then you can use these _pins_ to pick out the patterns you want:
+Then you can use these `pins` to pick out the patterns you want:
 
-   * _foo:1_ matches _foo:1,bar:zed-aaa_; _foo:1,bar:zed-bbb_; _foo:1,bar:zed-ccc_
-   * _foo:1, bar:*_ also matches _foo:1,bar:zed-aaa_; _foo:1,bar:zed-bbb_; _foo:1,bar:zed-ccc_
-   * _foo:1, bar:*-aaa_ matches only _foo:1,bar:zed-aaa_
+   * The pin <code>foo:1</code> matches the patterns <code>foo:1,bar:zed-aaa</code> and <code>foo:1,bar:zed-bbb</code> and <code>foo:1,bar:zed-ccc</code>
+   * The pin <code>foo:1, bar:*</code> also matches the patterns <code>foo:1,bar:zed-aaa</code> and <code>foo:1,bar:zed-bbb</code> and <code>foo:1,bar:zed-ccc</code>
+   * The pin <code>foo:1, bar:*-aaa</code> matches only the pattern <code>foo:1,bar:zed-aaa</code>
 
@@ -584,3 +582,3 @@ Let's extend the color service example. You'll have three separate
 handle incoming actions, and pass them on to the appropriate server by
-using a _pin_. The client will also define a new action that can
+using a <code>pin</code>. The client will also define a new action that can
 aggregate color lookups.
@@ -623,5 +621,5 @@
 This code calls the <code>client</code> method three times. Each time,
-it specifies an action pattern _pin_, and a destination port. And
+it specifies an action pattern <code>pin</code>, and a destination port. And
 action submitted to this Seneca instance via the <code>act</code>
-method will be matched against these _pin_ patterns. If there is a
+method will be matched against these <code>pin</code> patterns. If there is a
 match, they will not be processed locally. Instead they will be sent
@@ -687,6 +685,6 @@ out over the network to the micro-service that deals with them.
 _seneca-redis-transport_ will handle this for you so that you only
-have to think in terms of JavaScript objects
+have to think in terms of JavaScript objects.
 
 The JSON object is a wrapper for the message data. The wrapper contains
-some tracking fields to make debugging easier, these are:
+some tracking fields to make debugging easier. These are:
 
@@ -693,0 +691,0 @@ * _id_:     action identifier (appears in Seneca logs after IN/OUT)

Fixed alerts

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 1 instance in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Improved metrics

Number of low supply chain risk alerts

0

decreased by-100%

Number of medium supply chain risk alerts

3

decreased by-25%

Worsened metrics

Total package byte prevSize

71208

decreased by-38.97%

Number of package files

9

decreased by-79.55%

Lines of code

1038

decreased by-57.63%

Number of lines in readme file

963

decreased by-0.21%

Dependency changes

• + Addedlodash@4.15.0(transitive)

• - Removedlodash@4.14.2(transitive)

• Updatedlodash@4.15.0