Vercel Postgres, KV, Blob, and Edge Config
APACHE-2.0 License
Bot releases are visible (Hide)
Published by github-actions[bot] about 1 year ago
"types"
field from package.json to support "moduleResolution": "Node16"
Published by github-actions[bot] about 1 year ago
"types"
field from package.json to support "moduleResolution": "Node16"
Published by github-actions[bot] about 1 year ago
"types"
field from package.json to support "moduleResolution": "Node16"
Published by github-actions[bot] about 1 year ago
cacheControl
propertyPublished by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
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:
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
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 issueBlobCommandOptions
type is no longer exported. This is an internal utility type. Other internal types were removed also but nobody was using themmetadata
in onBeforeGenerateToken
and onUploadCompleted
has been renamed to tokenPayload
Enjoy!
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
b409aad: We added two new options on put()
:
addRandomSuffix: boolean
: Allows to disable or enable (default) randomcacheControlMaxAge: number
: Allows to configure the browser and edge cache,Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] over 1 year ago
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:
public.blob.vercel-storage.com/zyzoioy8txfs14xe/somefile-NoOVGDVcqSPc7VYCUAGnTzLTG2qEM2.txt
zyzoioy8txfs14xe.blob.vercel-storage.com/somefile-NoOVGDVcqSPc7VYCUAGnTzLTG2qEM2.txt
.put()
no more sends back size and uploadedAt, use .head() to get this.list()
no more sends back contentType and contentDisposition on the.del()
doesn't return any value (void). If the file was here prior toBlobResult
type has been splitted to PutBlobResult
for put() andHeadBlobResult
for head(). Use them accordingly.We've reworked our README to better surface the browser-upload and
server-upload methods.
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] over 1 year ago
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.
Published by github-actions[bot] over 1 year ago