vercel / nextjs-subscription-payments

Clone, deploy, and fully customize a SaaS subscription application with Next.js.
https://subscription-payments.vercel.app/
MIT License
5.77k stars 1.18k forks source link

Deploy error #341

Open hridaya423 opened 1 month ago

hridaya423 commented 1 month ago

Error: supabaseUrl is required.
--
16:49:50.780 | at new ag (/vercel/path0/.next/server/chunks/856.js:1:109603)
16:49:50.780 | at aw (/vercel/path0/.next/server/chunks/856.js:1:112826)
16:49:50.781 | at 37446 (/vercel/path0/.next/server/app/api/webhooks/route.js:1:72564)
16:49:50.781 | at t (/vercel/path0/.next/server/webpack-runtime.js:1:127)
16:49:50.781 | at r (/vercel/path0/.next/server/app/api/webhooks/route.js:1:112889)
16:49:50.781 | at /vercel/path0/.next/server/app/api/webhooks/route.js:1:112916
16:49:50.782 | at t.X (/vercel/path0/.next/server/webpack-runtime.js:1:1181)
16:49:50.784 | at /vercel/path0/.next/server/app/api/webhooks/route.js:1:112902
16:49:50.784 | at Object.<anonymous> (/vercel/path0/.next/server/app/api/webhooks/route.js:1:112944)
16:49:50.784 | at Module._compile (node:internal/modules/cjs/loader:1358:14)
16:49:50.789 |  
16:49:50.789 | > Build error occurred
16:49:50.791 | Error: Failed to collect page data for /api/webhooks
16:49:50.791 | at /vercel/path0/node_modules/.pnpm/next@14.1.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/utils.js:1258:15
16:49:50.791 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
16:49:50.791 | type: 'Error'
16:49:50.791 | }
16:49:50.807 | ELIFECYCLE  Command failed with exit code 1.
16:49:50.826 | Error: Command "pnpm run build" exited with 1

I have used the deploy button from github, followed all steps, as soon as i change anything in the github repo it fails, didnt touch the api/webhooks folder, just some footer changes and removing readme, and public files related to it. It worked before i changed anything.

hridaya423 commented 1 month ago

anyone else with this error, supabase key, url are production only whereas the deployment was in preview therefore failure