Releases: vercel/storage
Releases · vercel/storage
@vercel/[email protected]
Patch Changes
-
0c98feb: fix(blob): allow client uploads in web workers
Before this change, we had guards so client uploads could only be used in
browser environments, this prevented customers to use Vercel Blob in Web
Workers, sometimes React Native or in general anywhere window is not really what
we think it is.
@vercel/[email protected]
Minor Changes
- 7872e61: contentType default is now 'application/octet-stream' instead of
undefined
@vercel/[email protected]
Minor Changes
-
c3afec3: Add onUploadProgress feature to put/upload
You can now track the upload progress in Node.js and all major browsers when
using put/upload in multipart, non-multipart and client upload modes. Basically
anywhere in our API you can upload a file, then you can follow the upload
progress.Here's a basic usage example:
const blob = await put('big-file.pdf', file, { access: 'public', onUploadProgress(event) { console.log(event.loaded, event.total, event.percentage); } });
@vercel/[email protected]
Minor Changes
- d7ef349: Add the
consistentRead
option to allow reading from the origin. Note that it's not recommended to use this property without good reason due to the extrem performance cost.
@vercel/[email protected]
Patch Changes
- d58f9de: fix(blob): provide custom errors for expired client tokens and pathname mismatch
@vercel/[email protected]
Minor Changes
- 61b5939: BREAKING CHANGE, we're no more accepting non-encoded versions of ?, # and // in pathnames. If you want to use such characters in your pathnames then you will need to encode them.
@vercel/[email protected]
@vercel/[email protected]
Major Changes
- 14bc82e: BREAKING: Updates @upstash/redis to v1.34.0 which contains a small breaking change in the public API. The cursor field in scan commands is now returned as
string
instead ofnumber
.
@vercel/[email protected]
Minor Changes
- aaec8c5: Support new connection string format