Skip to content

Handle streaming contents #32

@phated

Description

@phated

I was reviewing a bunch of gulpfiles and many people do this (I know it's crazy but they do):

browserify.bundle()
  .pipe(vinylSourceStream())
  .pipe(vinylBuffer())
  .pipe(gulpSourcemaps.init())
  .pipe(gulpSourcemaps.write('./dist'))
  .pipe(gulp.dest('./dist'))

They seem to be buffering the contents just so they can write sourcemaps as individual files in the same directory as their output (as opposed to browserify's inline sourcemaps). If we support writing streaming sourcemaps in .dest(), they will only need vinylSourceStream() and can drop 3 steps (including buffering!!!) from their pipeline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions