Releases: muxinc/upchunk
v2.1.1: abort and more HTTP methods
A big part of this release is that we've added quite a few tests (and could always use more)! This will make it much easier for us to pull in changes quickly, so thanks for the contributions!
Changelog
Abort
@paulbellamy contributed a new abort
method. pause
remains unchanged and stops uploading after the in-flight chunk is done. The new abort
method pauses, but also cancels any in-flight XHR request.
More HTTP requests
@ickyicky contributed being able to use PATCH
or POST
requests instead of just PUT
when uploading each individual chunk.
chunkComplete
event
The old behavior of the progress
callback was that the event was fired after each chunk was successfully uploaded. This led to very "chunky" (ba dum tissss) progress updates, which is a big reason behind our switch to XHR in the 2.0 release. chunkComplete
brings back that functionality, allowing you to potentially save which chunks are complete or more.
v2.0.0: Upload progress between chunks
This release allows for the progress event to report intra-chunk upload progress. There should be no public API changes, simply update to 2.0 and your progress events will fire a lot more often! 😄
The API didn't change, why a major release?
In order to be able to reliably get upload progress for each request, we needed to switch to good ol' XHR instead of fetch
. This is a major release just in case anyone was relying on fetch
for polyfills or anything along those lines.
Enjoy!
v1.0.8
UpChunk can come to the SSR party now
No functional changes other than UpChunk won't blow things up when used in server-side rendered environments.
v1.0.6
v1.0.5
First Release!
v1.0.4 v1.0.4