next.js

f32d1acd - Fix pnpm-lock.yaml for bench/large-app-router after React upgrade (#101642)

Fix pnpm-lock.yaml for bench/large-app-router after React upgrade (#101642) ### What? Fixes the `pnpm-lock.yaml` entry for `bench/large-app-router` so that `pnpm install --frozen-lockfile` works on canary again. ### Why? Since #101502 was merged, canary CI (`build`, `build-next`, `fetch test timings`, `test devlow package`, …) fails at install with: ``` ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY Broken lockfile: no entry for 'lucide-react@0.554.0(react@19.3.0-canary-e84e1492-20261031)' in pnpm-lock.yaml ``` #101587 upgraded React to `19.3.0-canary-1620f7b9-20261111` while #101502 was open. The lockfile changes merged without a textual conflict. However, the new `bench/large-app-router` importer still referenced the `lucide-react` snapshot that was resolved against the old React version, and #101587 had removed that snapshot. ### How? Point the importer at the existing `lucide-react@0.554.0(react@19.3.0-canary-1620f7b9-20261111)` snapshot. This is a one-line lockfile change. ### Verification - On current canary with this change, `pnpm install --frozen-lockfile` succeeds. - A plain `pnpm install` leaves the lockfile unchanged ("Already up to date"). - `pnpm-lock.yaml` has no remaining references to `e84e1492`. <!-- NEXT_JS_LLM --> <!-- fleet 844a9209-a191-4c7b-904b-5f0ad1e6b91d --> Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>