docker-stream-cleanser - npm Package Compare versions

Comparing version 0.2.0 to 0.3.0

index.js

@@ -13,5 +13,7 @@ 'use strict';
  * @param  {string}       encoding stream data encoding
+ * @param  {string}       ignoreErrors true if errors should just be streamed through
+ * @param  {string}       logErrors true if errors should be logged to the console
  * @return {DuplexStream} pipe docker stream data through this duplex stream to remove headers
  */
-function createCleanserStream (encoding) {
+function createCleanserStream (encoding, ignoreErrors, logErrors) {
   encoding = encoding || 'utf8'; // utf8 is buffer default
@@ -22,2 +24,3 @@ var buffer = new Buffer('', encoding);
   var errored;
+  var allowErrors = !ignoreErrors;
 
@@ -44,4 +47,11 @@ function write (data) {
         if (currentType > 2) {
-          errored = true;
-          return self.emit('error', new Error('Recieved unexpected type in header: '+currentType));
+          errored = allowErrors;
+          buffer = Buffer.concat([header, buffer]);
+          bytesLeft = buffer.length;
+          if (logErrors) {
+            console.log('ERROR IN DSC:', buffer.toString());
+          }
+          if (allowErrors) {
+            self.emit('error', new Error('received unexpected type in header: ' + currentType));
+          }
         }
@@ -76,4 +86,4 @@ if (bytesLeft === 0) { // this reset is not necessary, but it is more explicit
     if (errored) { return; }
-    if (buffer.length) {
-      this.emit('error', new Error('End event recieved but buffer still has data'));
+    if (buffer.length && allowErrors) {
+      this.emit('error', new Error('End event received but buffer still has data'));
     }
@@ -80,0 +90,0 @@ else {

package.json

 {
   "name": "docker-stream-cleanser",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "main": "index.js",
@@ -5,0 +5,0 @@ "description": "This module cleans the docker headers from the log stream from a container.  I never found them very useful, so I wrote this to clean them up either in bulk, or in between a piping.  It's not as simple as just removing the first 8 bytes on every message",

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Lines of code

303

increased by3.41%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Total package byte prevSize

75360

decreased by-1.84%

No dependency changes