buffer-peek-stream
Advanced tools
Comparing version 0.2.0 to 1.0.0
# buffer-peek-stream changelog | ||
## 1.0.0 (2015/05/19) | ||
- no changes other than bump to a stable version | ||
## 0.2.0 (2014/11/12) | ||
@@ -4,0 +8,0 @@ |
{ | ||
"name": "buffer-peek-stream", | ||
"version": "0.2.0", | ||
"version": "1.0.0", | ||
"description": "Transform stream that lets you inspect the start of a ReadStream before deciding what to do with it", | ||
@@ -35,2 +35,2 @@ "main": "buffer-peek-stream.js", | ||
} | ||
} | ||
} |
# node-buffer-peek-stream | ||
A Transform stream which lets you take a peek at the first bytes before unpiping itself and unshifting the buffer back onto the upstream stream leaving the original stream ready to be | ||
[![Build Status](https://travis-ci.org/seangarner/node-buffer-peek-stream.svg?branch=master)](https://travis-ci.org/seangarner/node-buffer-peek-stream) | ||
A Transform stream which lets you take a peek at the first bytes before unpiping itself and | ||
unshifting the buffer back onto the upstream stream leaving the original stream ready to be | ||
piped again onto its final destination. | ||
@@ -48,9 +51,3 @@ | ||
## NOTICE | ||
This hasn't been run in production yet and hasn't gone through substantial testing. The approach | ||
taken to unshift data back onto the origin stream in particular could turn out to be a bad idea when | ||
you try to peek at more bytes than are in the stream. | ||
## Licence | ||
MIT |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage 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
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
9207
8
0
0
52