Re: Bug#915647: ITP: node-vinyl-source-stream -- Bridge that makes it simple to use conventional text streams
- Date: Wed, 5 Dec 2018 16:44:49 +0100
- From: Paolo Greppi <paolo.greppi@xxxxxxxxx>
- Subject: Re: Bug#915647: ITP: node-vinyl-source-stream -- Bridge that makes it simple to use conventional text streams
Il 05/12/18 16:13, Paulo Henrique de Lima Santana (phls) ha scritto:
> Package: wnpp
> Severity: wishlist
> Owner: "Paulo Henrique de Lima Santana (phls)" <phls@xxxxxxxxxxxxxxxxx>
> * Package name : node-vinyl-source-stream
> Version : 2.0.0
> Upstream Author : Hugh Kennedy <hughskennedy@xxxxxxxxx>
> * URL : https://github.com/hughsk/vinyl-source-stream
> * License : Expat
> Description : Bridge that makes it simple to use conventional text streams
> Use conventional text streams at the start of your gulp or vinyl pipelines,
> making for nicer interoperability with the existing npm stream ecosystem.
> Take, for example, browserify. There are the gulp-browserify and gulpify
> plugins, which you can use in combination with gulp to get browserify working
> in your build. Unfortunately, these plugins come with additional overhead:
> an extra GitHub repository, npm module, maintainer, tests, semantics, etc.
> It's much simpler in this case to use the original module directly where you
> can, which is what vinyl-source-stream handles for you.
> This is a Node.js module necessary to package a software name shellshare.
This is a simple module (single ES5 file, 26 LOC according to sloccount, no build steps required).
Although on npm register (https://www.npmjs.com/package/vinyl-source-stream) it has 767 dependents, until now we managed to avoid packaging it in Debian (https://codesearch.debian.net/search?q=vinyl-source-stream).
Possibly you can skip it too, by tweaking the gulpfile.js; but if you really need it, it could a good candidate for embedding, see: