Skip to content

Releases: vercel/storage

@vercel/blob@1.1.1

23 May 11:56
acaa9a0
Compare
Choose a tag to compare

Patch Changes

  • f65d3c9: copy, head and del can receive a blob url or pathname, until now it was not very clear.

@vercel/blob@1.1.0

22 May 11:03
f232754
Compare
Choose a tag to compare

Minor Changes

  • 2b4acc3: feat(blob): Add support for custom headers in client upload method

    This change adds the ability to pass custom headers to the upload method in the client, which will be forwarded to the server endpoint specified by handleUploadUrl. This is particularly useful for sending authorization headers and solves issues like #796 and #420.

@vercel/blob@1.0.2

19 May 14:19
1ade8df
Compare
Choose a tag to compare

Patch Changes

  • d3627fa: Update Vercel Blob API endpoint to a more efficient one

@vercel/blob@1.0.1

02 May 13:54
1634fd2
Compare
Choose a tag to compare

Patch Changes

  • af5f54b: Add correct documentation to all exported methods

@vercel/blob@1.0.0

10 Apr 15:00
0a62213
Compare
Choose a tag to compare

Major Changes

  • 00dfe23: Vercel Blob is now GA! To celebrate this we're releasing the 1.0.0 version of the Vercel Blob SDK which includes multiple changes and improvements.

    Changes:

    • addRandomSuffix is now false by default
    • Blobs are cached for one month, configurable and with a lower limit of 1 min. Which means you cannot configure the blob cache to be less than 1 minute.
    • Random suffixes are now also added to the pathname of blob responses and content-disposition header.
    • Overwriting blobs now requires to use allowOverwrite: true. Example:
    await put('file.png', file, { access: 'public' });
    
    await put('file.png', file, { access: 'public' }); // This will throw
    
    put('file.png', file, { access: 'public', allowOverwrite: true }); // This will work

    How to upgrade:

    • If you're using random suffixes by default, then add addRandomSuffix: true to put and onBeforeGenerateToken options.
    • If you're overwriting blobs, then add allowOverwrite: true to put and onBeforeGenerateToken options.
    • If you're using a cache-control of less than one minute, we recommend using a Vercel Function instead of a Blob. As Vercel Blob is primarily designed for caching content for a longer time.
    • If you're displaying the pathname field of Blob responses in a UI, and using random suffixes, make sure you adpat the UI to show the longer pathname.

@vercel/blob@0.27.3

13 Mar 14:27
a65d1b8
Compare
Choose a tag to compare

Patch Changes

  • f88d80b: Fix documentation links in README and types, no functional changes

@vercel/blob@0.27.2

27 Feb 14:57
29ec7cd
Compare
Choose a tag to compare

Patch Changes

  • 54ce5f8: Allow all special characters to be used as pathname.
    You can now use all the characters you want in pathname even the ones that have
    special meaning in urls like %!'()@{}[]# and it will work as expected.

@vercel/blob@0.27.1

17 Jan 16:17
8c02df6
Compare
Choose a tag to compare

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/blob@0.27.0

04 Dec 15:12
905fbd4
Compare
Choose a tag to compare

Minor Changes

  • 7872e61: contentType default is now 'application/octet-stream' instead of undefined

@vercel/blob@0.26.0

06 Nov 15:32
3b691bd
Compare
Choose a tag to compare

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);
      }
    });
    

    Fixes #543
    Fixes #642