v3.4.0

• Feature: Add useLargeFileWorkaround option to fallback to reading entire file into memory for cases where ReadableStream fails due to file size.

v3.3.3

• Fix: Clean up some error state edge cases.
• Fix: Re-notify progress for failed chunk uploads
• Fix: Clean up offline state cases and expose offline as a readonly property
• Fix: Account for error case and notify error for failures on ReadableStream::getReader() read() (e.g. https://bugs.webkit.org/show_bug.cgi?id=272600)

v3.3.2

What's Changed

• Add response objects into failure events details. by @mr-sanders in #129

New Contributors

• @mr-sanders made their first contribution in #129

v3.3.1

Bug Fixes

• Use Range response header to ensure all bytes were received. by @skidder in #125

New Contributors

• @skidder made their first contribution in #125

Full Changelog: v3.3.0...v3.3.1

UMD dist bundles

• Replaces a simple iife bundle with a umd-based equivalent in order to have a better support matrix for build tools and related that don't yet respect things like exports package.json.

Change createUpload export to work around build issues

• Includes changes from @mmvsk #115
• Suspect this will either fully or partially solve the issues brought up in #88

UpChunk.createUpload static method

• Feat: Adds createUpload as a static method to the UpChunk class definition for easier import usage and JS class conventions.

Support custom headers

This release adds the ability to add extra custom headers via the headers config property, either as a static set of a headers or a function that (synchronously or asynchronously) yields the headers.

Bug Fix for Min/Max Chunksize

Bug was introduced that improperly applied min/max chunk size. Relevant for dynamic chunk sizing.

TypeScript Compatibility Fixes

Fix: Refactored to use some older TypeScript syntax to ensure greater backwards compatibility.