mafintosh/pump

Issues

• The latest update throws an exception in older versions of nodejs

  #59 opened 4 months ago by rossroma
  2

• Browser Support

  #6 opened 9 years ago by wesleytodd
  12

• use `pump(zipStream, writeStream)`, the zip file at disk is nested one level more

  #57 opened 3 years ago by WormGirl
  1

• Incrementally pipe additional streams & handle split streams

  #56 opened 3 years ago by wholenews
  2

• Question: when not to use `pump`?

  #52 opened 5 years ago by DenisFrezzato
  6

• Qustion: use pump with substreams

  #12 opened 4 years ago by RWander
  1

• Current project status

  #46 opened 4 years ago by DanielRuf
  6

• Error are not triggered

  #54 opened 5 years ago by leecjson
  2

• Option to not end dest?

  #26 opened 7 years ago by ronag
  3

• Async errors not caught in Node < 10

  #51 opened 5 years ago by richardscarrott
  0

• Pump closes the stream after just 16 iterations

  #49 opened 5 years ago by autocorrectoff
  2

• Question: Is pump compatible with the request library?

  #48 opened 6 years ago by JAndritsch
  6

• callback in pump firing before _flush complete

  #47 opened 6 years ago by andrewnaeve
  2

• pump swallowing errors when read stream is empty

  #45 opened 6 years ago by coderaiser
  2

• Consider switching to promise based API

  #11 opened 8 years ago by LinusU
  3

• Reduce the size of the npm package by limiting the included files

  #44 opened 6 years ago by paazmaya
  0

• How to propagate errors in pipe using pump?

  #43 opened 6 years ago by rstor1
  0

• MaxListenersExceededWarning: Possible EventEmitter memory leak detected

  #42 opened 6 years ago by amitguptagwl
  1

• bring into node core

  #17 opened 6 years ago by calvinmetcalf
  7

• Multiple pumps inside a single task

  #28 opened 7 years ago by janrembold
  4

• This module is now part of Node.js 10

  #40 opened 7 years ago by ehmicky
  3

• pump + webpack-stream exits watch task

  #39 opened 7 years ago by janrembold
  2

• Callback is called when destination file is still open if source stream emits error

  #38 opened 7 years ago by sekogan
  0

• buffered data in readable stream does not reach writable stream

  #33 opened 7 years ago by lpinca
  3

• Pass error in stream.destroy()

  #35 opened 7 years ago by BenoitClaveau
  0

• returning last stream

  #27 opened 7 years ago by pgte
  5

• http2

  #22 opened 7 years ago by ronag
  0

• "premature close" error when calling destroy on source stream

  #25 opened 7 years ago by harishvadali
  3

• Consider returning undefined instead of a stream

  #9 opened 7 years ago by phated
  8

• Use pump with a Transform Stream as final stream object

  #24 opened 7 years ago by sprijk
  6

• pump on "unclosable" stream

  #20 opened 7 years ago by allevo
  2

• Callback not called with stdout/stderr

  #19 opened 8 years ago by julien-f
  2

• Question: "Error: task completion callback called too many times"

  #16 opened 8 years ago by roberttolton
  3

• Arrays-in-arrays to create reuseable functions

  #15 opened 8 years ago by elygre
  2

• Webpack !fs issue

  #14 opened 8 years ago by aakilfernandes
  2

• pump with series tasks

  #10 opened 8 years ago by HASSANDL
  1

• stream remains active after pump callback when error does not terminate stream

  #8 opened 8 years ago by pabigot
  1

• Pump synchronized ?

  #7 opened 8 years ago by Elfayer
  2

• objectMode piping?

  #3 opened 9 years ago by yoshuawuyts
  3

• pump throttle

  #1 opened 9 years ago by dcerisano
  3