vrs

Summary The Vercel project is configured for Node.js , but builds were failing because declared an range capped at Node 16, so refused to run on the build image. Once that was unblocked, the build still crashed during static page generation because constructed the Airtable client at module import time, even when had been removed from the environment. This change makes the project deploy cleanly on the current Vercel runtime without expanding scope: Bump from to and from to . Both are the latest patch releases on the existing major lines and remove the Node engine restriction that broke the install step. They also pull in patch-level security fixes for the underlying auth and rendering stacks (, , , , , , etc.). _(see note below)_ Refresh so the patched dependency graph is reproducible on Vercel. Make the Airtable client lazy in . The static / paths now skip Airtable entirely and fall back to whenever any of , , , or is unset, instead of throwing during module import. React stays at , which is already the latest patch on the React 17 line, so no React change is needed. ℹ️ - There is still outstanding advisory risk on the side. is the latest patch release on the current major line, but known Next.js advisories remain on 12.x and are not fully remediable with another in-line patch bump. The follow-up path is a broader framework upgrade to while staying on the Pages Router, plus / , cleanup of legacy usage, image config updates, and regression testing for the editor / 3D / auth / checkout flows.