vinyl-source-stream

WebJar for vinyl-source-stream

License

License

MIT
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

vinyl-source-stream
Last Version

Last Version

1.1.0
Release Date

Release Date

Type

Type

jar
Description

Description

vinyl-source-stream
WebJar for vinyl-source-stream
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/hughsk/vinyl-source-stream

Download vinyl-source-stream

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/vinyl-source-stream/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>vinyl-source-stream</artifactId>
    <version>1.1.0</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/vinyl-source-stream/
implementation 'org.webjars.npm:vinyl-source-stream:1.1.0'
// https://jarcasting.com/artifacts/org.webjars.npm/vinyl-source-stream/
implementation ("org.webjars.npm:vinyl-source-stream:1.1.0")
'org.webjars.npm:vinyl-source-stream:jar:1.1.0'
<dependency org="org.webjars.npm" name="vinyl-source-stream" rev="1.1.0">
  <artifact name="vinyl-source-stream" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='vinyl-source-stream', version='1.1.0')
)
libraryDependencies += "org.webjars.npm" % "vinyl-source-stream" % "1.1.0"
[org.webjars.npm/vinyl-source-stream "1.1.0"]

Dependencies

compile (2)

Group / Artifact Type Version
org.webjars.npm : vinyl jar [0.4.3,0.5)
org.webjars.npm : through2 jar [0.6.1,0.7)

Project Modules

There are no modules declared in this project.

vinyl-source-stream Flattr this!experimental

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.

Usage

vinyl-source-stream

Our previous example, browserify, has a streaming API for its output bundles which you can use directly. This module is just a bridge that makes it simple to use conventional text streams such as this in combination with gulp. Here's an example of using vinyl-source-stream and browserify, compared to using gulpify:

var source = require('vinyl-source-stream')
var streamify = require('gulp-streamify')
var browserify = require('browserify')
var uglify = require('gulp-uglify')
var gulpify = require('gulpify')
var rename = require('gulp-rename')
var gulp = require('gulp')

// using gulpify:
gulp.task('gulpify', function() {
  gulp.src('index.js')
    .pipe(gulpify())
    .pipe(uglify())
    .pipe(rename('bundle.js'))
    .pipe(gulp.dest('./'))
})

// using vinyl-source-stream:
gulp.task('browserify', function() {
  var bundleStream = browserify('./index.js').bundle()

  bundleStream
    .pipe(source('index.js'))
    .pipe(streamify(uglify()))
    .pipe(rename('bundle.js'))
    .pipe(gulp.dest('./'))
})

Not all that different, really! The nice thing here is that you're getting the up-to-date browserify API and don't have to worry about the plugin's available functionality. Of course, these same benefits apply for any readable text stream you can find on npm.

API

stream = sourceStream([filename])

Creates a through stream which takes text as input, and emits a single vinyl file instance for streams down the pipeline to consume.

filename is a "pretend" filename to use for your file, which some streams might use to determine various factors such as the final filename of your file. It should be a string, and though recommended, using this argument is optional.

License

MIT. See LICENSE.md for details.

Versions

Version
1.1.0