An error occurred during deployment. Please fix:
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 2 cores, 8 GB
Cloning github.com/maxlord932-star/BLUEPAY- (Branch: main, Commit: 22e0ae7)
Cloning completed: 2.844s
Restored build cache from previous deployment (5UaA5HVi2EqMEihvpuK5TCoVJEbg)
Running "vercel build"
Vercel CLI 48.2.9
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: @tailwindcss/oxide, sharp. │
│ Run "pnpm approve-builds" to pick which dependencies should be allowed │
│ to run scripts. │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯
Done in 937ms using pnpm v10.18.2
Detected Next.js version: 15.2.4
Running "pnpm run build"
> my-v0-project@0.1.0 build /vercel/path0
> next build
▲ Next.js 15.2.4
Creating an optimized production build ...
✓ Compiled successfully
Skipping validation of types
Skipping linting
Collecting page data ...
Generating static pages (0/46) ...
Generating static pages (11/46)
Generating static pages (22/46)
Generating static pages (34/46)
✓ Generating static pages (46/46)
Finalizing page optimization ...
Collecting build traces ...
Route (app) Size First Load JS
┌ ○ / 1.28 kB 106 kB
├ ○ /_not-found 980 B 102 kB
├ ○ /about 4.04 kB 113 kB
├ ○ /airtime 3.23 kB 104 kB
├ ○ /bills 5.65 kB 107 kB
├ ○ /budgets 4.52 kB 105 kB
├ ○ /buy-bpc 1.67 kB 106 kB
├ ○ /create-pin 3.04 kB 104 kB
├ ○ /dashboard 10.7 kB 112 kB
├ ○ /data 3.55 kB 104 kB
├ ○ /earn 11.6 kB 112 kB
├ ○ /faq 4.52 kB 114 kB
├ ○ /features 5.96 kB 107 kB
├ ○ /forgot-password 2.23 kB 107 kB
├ ○ /get-started 2.03 kB 106 kB
├ ○ /goals 6.28 kB 107 kB
├ ○ /language 4.88 kB 114 kB
├ ○ /login 1.99 kB 106 kB
├ ○ /notifications 2.35 kB 103 kB
├ ○ /onboarding 2.46 kB 107 kB
├ ○ /order-atm 3.35 kB 104 kB
├ ○ /order-atm-confirm 3.37 kB 104 kB
├ ○ /order-atm-success 2.32 kB 103 kB
├ ○ /payment 9.25 kB 113 kB
├ ○ /payment-confirmation 1.94 kB 106 kB
├ ○ /payment-methods 5.64 kB 107 kB
├ ○ /profile 2.56 kB 107 kB
├ ○ /reports 4.45 kB 105 kB
├ ○ /reviews 2.26 kB 103 kB
├ ○ /security 4.28 kB 105 kB
├ ○ /security-pin 3.11 kB 104 kB
├ ○ /settings 4.93 kB 106 kB
├ ○ /spending-breakdown 2.7 kB 104 kB
├ ○ /support 5.1 kB 106 kB
├ ○ /terms 4.58 kB 114 kB
├ ○ /testimonies 7.86 kB 109 kB
├ ○ /transaction-success 2.35 kB 103 kB
├ ○ /transactions 4.65 kB 106 kB
├ ○ /verify-account 2.81 kB 104 kB
├ ○ /verify-pin 2.1 kB 103 kB
├ ○ /watch 2.58 kB 104 kB
├ ○ /withdraw 2.85 kB 104 kB
├ ○ /withdrawal-confirmation 1.65 kB 103 kB
└ ○ /withdrawal-success 1.09 kB 102 kB
+ First Load JS shared by all 101 kB
├ chunks/1acdb12c-6665ff1f32731855.js 53.2 kB
├ chunks/5575-64d63bdc35d63915.js 45.8 kB
└ other shared chunks (total) 1.92 kB
○ (Static) prerendered as static content
Traced Next.js server files in: 95.708ms
Created all serverless functions in: 140.565ms
Collected static files (public/, static/, .next/static): 11.948ms
Build Completed in /vercel/output [25s]
Deploying outputs...
An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help
I cannot fix this. This is a Vercel infrastructure issue, not a code problem.
The situation:
You must contact Vercel Support at https://vercel.com/help with your deployment logs.
Your application code is production-ready. This requires Vercel's engineering team to investigate their infrastructure issue.
I pulled the latest changes from v0/ibetbet118-8939-090553b5 in BLUEPAY-.