Skip to content

Releases: nathanpeck/s3-upload-stream

v1.0.6

20 Oct 16:16
Compare
Choose a tag to compare

Removing global state from the package, and adding support to pause and resume multipart uploads.

v1.0.5

20 Oct 16:15
Compare
Choose a tag to compare

Minor browser support patch.

v1.0.4

13 Oct 15:02
Compare
Choose a tag to compare

Getting rid of the use of setImmediate. Also now the MPU is not initialized until data is actually received by the writable stream, and error checking verifies that data has actually been uploaded to S3 before trying to end the stream. This fixes an issue where empty incoming streams were causing errors to come back from S3 as the module was attempting to complete an empty MPU.

v1.0.2

26 Sep 15:07
Compare
Choose a tag to compare

Emitting a "finish" even to adhere to Node.js writable stream spec.

v1.0.1

26 Sep 15:06
Compare
Choose a tag to compare

Fixing messed up examples and documentation that did not use the "new" keyword when instantiating the stream. Following the incorrect example caused issues when running multiple uploads in parallel.

v1.0.0

15 Sep 20:37
Compare
Choose a tag to compare

Major overhaul of the functional interface. Breaks compatibility with older versions of the module in favor of a cleaner, more streamlined approach. A migration guide for users of older versions of the module has been included in the documentation.

v0.6.2

31 Aug 23:23
Compare
Choose a tag to compare

Upgrading the AWS SDK dependency to the latest version. Fixes issue #11

v0.6.1

22 Aug 14:05
Compare
Choose a tag to compare
  • Fix for issue #10, which was caused by improper use of EventEmitter for events internal to the module. This was a critical bug affecting v0.6.0 and v0.5.0.

v0.6.0

15 Aug 16:27
Compare
Choose a tag to compare
  • Fix for mismatch between documentation and reality in the maxPartSize() and concurrentParts() options.
  • New feature: part size and concurrect part helpers can be chained now.

v0.5.0

13 Aug 20:29
Compare
Choose a tag to compare
  • Added client caching to reuse an existing s3 client rather than creating a new one for each upload. Fixes #6
  • Updated the maxPartSize to be a hard limit instead of a soft one so that generated ETAG's are consistent due to the reliable size of the uploaded parts. Fixes #7
  • Added a changelog.md file. Fixes #8
  • New feature: concurrent part uploads. Now you can optionally enable concurrent part uploads if you wish to allow your application to drain the source stream more quickly and absorb some of the backpressure from a fast incoming stream when uploading to S3.