storage

Patch Changes

• d90e973: Removed "types" field from package.json to support "moduleResolution": "Node16"

Patch Changes

• 3105f2b: make parseConnectionString parse both internal and external connection strings
• d90e973: Removed "types" field from package.json to support "moduleResolution": "Node16"

Patch Changes

• d90e973: Removed "types" field from package.json to support "moduleResolution": "Node16"

Patch Changes

• c0fe4e7: vercelBlob.head() now sends a cacheControl property

Patch Changes

• 15f7eef: Fix types for old module resolution. Before this commit types for the main package would be imported with a dot in the import path on autocompletion.

Patch Changes

• ae93246: Fix `Cannot find module '@vercel/blob/client' errors for JavaScript projects or TypeScript projects with an old moduleResolution setting.

Minor Changes

• e01f1ef: add stale-if-error semantics

Minor Changes

• 8251462: This release introduces BREAKING CHANGES. Mostly, we've separated client and server needs better. While ensuring we only export what we currently think is useful to you.

  We have a completely new documentation about client (browser) uploads: https://vercel.com/docs/storage/vercel-blob/quickstart#client-uploads.

  We've moved and renamed client-related utilities, including the ones to generate client tokens, to a separate entry file: @vercel/blob/client. Use it this way:

  import {
    upload,
    handleUpload,
    generateClientTokenFromReadWriteToken,
  } from '@vercel/blob/client';
  

  Here are the new features:

  • You can now pass a clientPayload?: string option during client uploads via the upload method. This payload can be used to attach metadata to your file, for example when updating a blog post cover image, you may want to pass: clientPayload: JSON.stringify({ postId: 123 }), so you can then use it server side to update the blog post.

  Here are the BREAKING CHANGES:

  • handleBlobUpload has moved to client/handleUpload
  • For client (browser) uploads, please use client/upload instead of put. Also, the handleBlobUploadUrl option has been renamed to handleUploadUrl.
  • verifyCallbackSignature is no more exported if you think you need it, open an issue
  • BlobCommandOptions type is no longer exported. This is an internal utility type. Other internal types were removed also but nobody was using them
  • metadata in onBeforeGenerateToken and onUploadCompleted has been renamed to tokenPayload

  Enjoy!

Minor Changes

• cedd4b9: adds connection info to edge config clients

Minor Changes

• b409aad: We added two new options on put():

  • addRandomSuffix: boolean: Allows to disable or enable (default) random
    suffixes added to file paths
  • cacheControlMaxAge: number: Allows to configure the browser and edge cache,
    in seconds. Default to one year (browser) and 5 minutes (edge). The edge cache
    is currently always set to a maximum of 5 minutes. But can be lowered to 0

Patch Changes

• 6104c9f: Upgrade to latest neon database driver
• Updated dependencies [6104c9f]
  • @vercel/[email protected]

Patch Changes

• 6104c9f: Upgrade to latest neon database driver

Minor Changes

• e273673: BREAKING CHANGE: Some methods responses and types have been updated following a
  migration Vercel did to make Vercel Blob more robust and closer to the S3 API.

  Namely:

  • the urls generated by Vercel Blob have moved from:
    public.blob.vercel-storage.com/zyzoioy8txfs14xe/somefile-NoOVGDVcqSPc7VYCUAGnTzLTG2qEM2.txt
    to
    zyzoioy8txfs14xe.blob.vercel-storage.com/somefile-NoOVGDVcqSPc7VYCUAGnTzLTG2qEM2.txt
    This change has been done transparently: all previous blob urls are
    redirected to the new domain.
  • .put() no more sends back size and uploadedAt, use .head() to get this
    information. Refer to the PutBlobResult type.
  • .list() no more sends back contentType and contentDisposition on the
    blobs property. Refer to the ListBlobResult type.
  • .del() doesn't return any value (void). If the file was here prior to
    a del() call, then it's now deleted.
  • BlobResult type has been splitted to PutBlobResult for put() and
    HeadBlobResult for head(). Use them accordingly.

  We've reworked our README to better surface the browser-upload and
  server-upload methods.

Patch Changes

• 978a817: Added an API version string when activated, related to multi bucket migration, no need to update for now.

Minor Changes

• Upgrade @neon/serverless to the latest version
  Automatically uses @neon http layer with Pool.query/sql``
  Stop minifying and add sourcemaps for better debugging

Patch Changes

• Updated dependencies [f545e1c]
  • @vercel/[email protected]

Minor Changes

• Upgrade @neon/serverless to the latest version
  Automatically uses @neon http layer with Pool.query/sql``
  Stop minifying and add sourcemaps for better debugging

Patch Changes

• f545e1c: Upgrade @upstash/redis to the latest version
  Stop minifying and add sourcemaps for better debugging

Patch Changes

• Updated dependencies [52ce540]
  • @vercel/[email protected]

Patch Changes

• 52ce540: Before this release, when using our default pooling client (import { sql } from '@vercel/storage'), and deploying on Vercel Edge Functions,
  then your Edge Functions would timeout after 11 requests.

  Full explanation: we set node-postgres Pool maxUses parameter to 1 in Edge Function, because clients can't be reused between requests in this serverless context.
  This combined with how our module is made (a JavaScript proxy) triggered a specific condition where clients would never be released to the Pool.

  The exact line that failed under these circumstances was: https://github.com/brianc/node-postgres/blob/735683c5cb41bcbf043c6490be4b7f38cfe3ac48/packages/pg-pool/index.js#L166

  This is now fixed, thanks @cramforce.

Patch Changes

• ce4b585: Add handleBlobUpload wrapper