Update buffer-pipe to the latest version 🚀

[greenkeeper]

Version 0.0.3 of buffer-pipe was just published.

Dependency	buffer-pipe
Current Version	0.0.2
Type	dependency

The version 0.0.3 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of buffer-pipe.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 7 commits.

• 6e4d367 0.0.3
• 52c0648 updated deps
• 25c3fa9 subarray -> slice
• 5d5421d Merge pull request #4 from wanderer/greenkeeper/nyc-12.0.1
• 392d8cf chore(package): update nyc to version 12.0.1
• 9f9b244 Merge pull request #2 from wanderer/greenkeeper/standard-11.0.0
• d347b23 chore(package): update standard to version 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[coveralls]

Coverage remained the same at 100.0% when pulling 7c41294 on greenkeeper/buffer-pipe-0.0.3 into a649037 on master.

[greenkeeper]

• The dependency buffer-pipe was updated from 0.0.2 to 0.0.4.

Update to this version instead 🚀

[greenkeeper]

• The dependency buffer-pipe was updated from 0.0.2 to 0.0.5.

Update to this version instead 🚀