Releases: vercel/storage
Releases · vercel/storage
@vercel/blob@0.26.0
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/edge-config@1.4.0
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/blob@0.25.1
Patch Changes
- d58f9de: fix(blob): provide custom errors for expired client tokens and pathname mismatch
@vercel/blob@0.25.0
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/blob@0.24.1
@vercel/kv@3.0.0
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/edge-config@1.3.0
Minor Changes
- aaec8c5: Support new connection string format
@vercel/blob@0.24.0
@vercel/postgres@0.10.0
Minor Changes
- a2a4757: Removes utf-8-validate dependency and sets minimum Node.js version to 18.14