7ebff31475
Version 3 of the kit: - Radix UI replaced with Base UI (using the Shadcn UI patterns) - next-intl replaces react-i18next - enhanceAction deprecated; usage moved to next-safe-action - main layout now wrapped with [locale] path segment - Teams only mode - Layout updates - Zod v4 - Next.js 16.2 - Typescript 6 - All other dependencies updated - Removed deprecated Edge CSRF - Dynamic Github Action runner
15 lines
832 B
Plaintext
15 lines
832 B
Plaintext
---
|
|
status: "published"
|
|
title: 'Troubleshooting deployment issues in the Next.js Supabase kit'
|
|
label: 'Deployment'
|
|
order: 4
|
|
description: 'Troubleshoot issues related to deploying the application in the Next.js Supabase SaaS kit'
|
|
---
|
|
|
|
## The deployment build fails
|
|
|
|
This is most likely an issue related to the environment variables not being set correctly in the deployment environment. Please analyse the logs of the deployment provider to see what is the issue.
|
|
|
|
The kit is very defensive about incorrect environment variables, and will throw an error if any of the required environment variables are not set. In this way - the build will fail if the environment variables are not set correctly - instead of deploying a broken application.
|
|
|
|
If you are deploying to Vercel, [please follow this guide](../going-to-production/vercel). |