strtus/Vercel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix client-side Vercel Blob fallback never executing

Browse Source 
HAS_VERCEL_BLOB_STORAGE depends on BLOB_READ_WRITE_TOKEN which is a
server-only env var (not NEXT_PUBLIC_*), so it evaluates to false in
the browser. When the R2 presigned-URL PUT fails (e.g. due to missing
CORS on the R2 bucket), the fallback branch was unreachable and the
original "Failed to fetch" error propagated to the UI.

vercelBlobUploadFromClient works client-side because it obtains the
token via a server round-trip to handleUploadUrl, so try it
unconditionally as a fallback.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Strtus 2026-05-19 10:54:33 +08:00
parent 66fa66d3d3
commit 0ac550c039
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/platforms/storage/index.ts
View File

@ -160,12 +160,15 @@ export const uploadFileFromClient = async (
try {
return await uploadFromClientViaPresignedUrl(file, fileName);
} catch (error) {
// Fall back to Vercel Blob when configured, so uploads stay available
// even if third-party object storage is temporarily unreachable.
if (HAS_VERCEL_BLOB_STORAGE) {
return vercelBlobUploadFromClient(file, fileName);
// HAS_VERCEL_BLOB_STORAGE relies on BLOB_READ_WRITE_TOKEN which is a
// server-only variable (not NEXT_PUBLIC_*), so it is always false in
// the browser. vercelBlobUploadFromClient only needs the server-side
// token via handleUploadUrl, so try it unconditionally as a fallback.
try {
return await vercelBlobUploadFromClient(file, fileName);
} catch {
throw error;
}
throw error;
}
}