[pull] canary from vercel:canary#1042
Merged
Merged
Conversation
## Summary Replaces the Cloudinary-backed image gallery example with a Vercel Blob–backed equivalent. The migration is driven by the broader move of [`vercel/nextconf-image-gallery`](https://github.com/vercel/nextconf-image-gallery) (the deployed companion to this example) off Cloudinary. - Renamed `examples/with-cloudinary` → `examples/with-vercel-blob` via `git mv` (history preserved). - Images are discovered at build time via the `@vercel/blob` SDK's `list()` API, then probed with [`sharp`](https://github.com/lovell/sharp) for dimensions and to pre-generate base64 blur placeholders. `next/image` (Vercel's image optimizer) handles resizing — no Cloudinary `c_scale,w_*` transform URLs. - `ImageProps` is now `{ id, url, width, height, blurDataUrl }` (was `{ public_id, format, ... }`). - `utils/cachedImages.ts` does the listing + dimension probe + blur placeholder generation. - Removed `utils/cloudinary.ts` and `utils/generateBlurPlaceholder.ts`. - `next.config.js` `remotePatterns` now allows `*.public.blob.vercel-storage.com`. - Deps: dropped `cloudinary`, `imagemin`, `imagemin-jpegtran`; added `@vercel/blob` and `sharp`. - `.env.local.example` reduced to a single `BLOB_READ_WRITE_TOKEN`. - README rewritten: blob description, deploy-button env, setup steps, references. ## Test plan - [x] `npx create-next-app --example with-vercel-blob ./blob-app` clones cleanly - [x] After populating a blob store and `.env.local`, `npm run dev` renders the gallery with blur placeholders - [x] `npm run build` succeeds (sharp probe + placeholder generation runs at build time) - [x] Vercel deploy button flow prompts only for `BLOB_READ_WRITE_TOKEN` --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
The devIndicator page doesn't really show that this is used in next.config.js - in isolation an agent might not infer the right usage.
## What? Converts existing `createNext()` usage into `nextTestSetup()`. `createNext()` was the setup step we had before `nextTestSetup()` was added. This PR focused on the simple conversion cases. There will be a follow-up to complete the last few. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )