Neon 部署错误 - v0 by Vercel

Running build in Washington, D.C., USA (East) – iad1 Build machine configuration: 2 cores, 8 GB Retrieving list of deployment files... Downloading 134 deployment files... Restored build cache from previous deployment (GSUeEeJV1CnEseP5QNZhPx3mb4fj) Running "vercel build" Vercel CLI 50.28.0 Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x Using pnpm@10.x based on project creation date To use pnpm@9.x, manually opt in using corepack (https://vercel.com/docs/deployments/configure-a-build#corepack) Installing dependencies... Lockfile is up to date, resolution step is skipped Already up to date ╭ Warning ─────────────────────────────────────────────────────────────────────╮ │ │ │ Ignored build scripts: sharp@0.34.5. │ │ Run "pnpm approve-builds" to pick which dependencies should be allowed │ │ to run scripts. │ │ │ ╰──────────────────────────────────────────────────────────────────────────────╯ Done in 1s using pnpm v10.28.0 Detected Next.js version: 16.1.6 Running "pnpm run build" > my-project@0.1.0 build /vercel/path0 > next build ▲ Next.js 16.1.6 (Turbopack) Creating an optimized production build ... ✓ Compiled successfully in 8.8s Skipping validation of types We detected TypeScript in your project and reconfigured your tsconfig.json file for you. The following suggested values were added to your tsconfig.json. These values can be changed to fit your project's needs: - include was updated to add '.next/dev/types/**/*.ts' Collecting page data using 1 worker ... Generating static pages using 1 worker (0/36) ... Generating static pages using 1 worker (9/36) Generating static pages using 1 worker (18/36) Error occurred prerendering page "/register". Read more: https://nextjs.org/docs/messages/prerender-error ReferenceError: Building2 is not defined at p (.next/server/chunks/ssr/[root-of-the-server]__c09afd1c._.js:1:17193) { digest: '3503849399' } Export encountered an error on /register/page: /register, exiting the build. ⨯ Next.js build worker exited with code: 1 and signal: null ELIFECYCLE Command failed with exit code 1. Error: Command "pnpm run build" exited with 1

Running build in Washington, D.C., USA (East) – iad1 Build machine configuration: 2 cores, 8 GB Retrieving list of deployment files... Downloading 134 deployment files... Restored build cache from previous deployment (GSUeEeJV1CnEseP5QNZhPx3mb4fj) ... } Export encountered an error on /register/page: /register, exiting the build. ⨯ Next.js build worker exited with code: 1 and signal: null ELIFECYCLE Command failed with exit code 1. Error: Command "pnpm run build" exited with 1

An error occurred during deployment. Please fix:

Running build in Washington, D.C., USA (East) – iad1  
Build machine configuration: 2 cores, 8 GB  
Retrieving list of deployment files...  
Downloading 134 deployment files...  
Restored build cache from previous deployment (GSUeEeJV1CnEseP5QNZhPx3mb4fj)  
Running "vercel build"  
Vercel CLI 50.28.0  
Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x  
Using pnpm@10.x based on project creation date  
To use pnpm@9.x, manually opt in using corepack (https://vercel.com/docs/deployments/configure-a-build#corepack)  
Installing dependencies...  
Lockfile is up to date, resolution step is skipped  
Already up to date  
  
╭ Warning ─────────────────────────────────────────────────────────────────────╮  
│                                                                              │  
│   Ignored build scripts: sharp@0.34.5.                                       │  
│   Run "pnpm approve-builds" to pick which dependencies should be allowed     │  
│   to run scripts.                                                            │  
│                                                                              │  
╰──────────────────────────────────────────────────────────────────────────────╯  
Done in 1s using pnpm v10.28.0  
Detected Next.js version: 16.1.6  
Running "pnpm run build"  
  
> my-project@0.1.0 build /vercel/path0  
> next build  
  
▲ Next.js 16.1.6 (Turbopack)  
  
  Creating an optimized production build ...  
✓ Compiled successfully in 8.8s  
  Skipping validation of types  
  
  We detected TypeScript in your project and reconfigured your tsconfig.json file for you.  
  The following suggested values were added to your tsconfig.json. These values can be changed to fit your project's needs:  
  
  	- include was updated to add '.next/dev/types/**/*.ts'  
  
  Collecting page data using 1 worker ...  
  Generating static pages using 1 worker (0/36) ...  
  Generating static pages using 1 worker (9/36) 
  
  Generating static pages using 1 worker (18/36) 
  
Error occurred prerendering page "/register". Read more: https://nextjs.org/docs/messages/prerender-error  
ReferenceError: Building2 is not defined  
    at p (.next/server/chunks/ssr/[root-of-the-server]__c09afd1c._.js:1:17193) {  
  digest: '3503849399'  
}  
Export encountered an error on /register/page: /register, exiting the build.  
⨯ Next.js build worker exited with code: 1 and signal: null  
 ELIFECYCLE  Command failed with exit code 1.  
Error: Command "pnpm run build" exited with 1