fix: resolve deployment blockers for Vercel#109
Merged
Conversation
- .vercelignore: stop excluding postcss.config.js, tailwind.config.ts, and tsconfig*.json which are required during the Vercel build step - .vercelignore: fix eslint config filename (eslint.config.js → eslint.config.mjs) - AGENTS.md: fix next.config.ts → next.config.js reference - VERCEL_DEPLOYMENT_GUIDE.md: replace npm commands with pnpm per project rules - .gitignore: fix misleading 'use npm only' comment Note: Guardian workflow (main.yml) also needs fixes but requires workflow scope to push — see PR description for manual steps. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates Vercel deployment-related configuration and documentation to align with pnpm usage, correct file references, and ensure build-critical files are included in Vercel deployments. Flow diagram for Vercel build behavior with corrected .vercelignoreflowchart TD
Dev[Developer_merges_PR] --> VercelHook["Vercel_git_hook_triggers_deploy"]
VercelHook --> Collect["Collect_files_respecting_.vercelignore"]
Collect -->|includes_tailwind.config.ts_postcss.config.js_tsconfig*.json| Build["Run_pnpm_run_db_generate_and_pnpm_run_build"]
Build --> NextBuild["next_build_executes"]
NextBuild --> CSS["Tailwind_CSS_compilation_uses_tailwind.config.ts_and_postcss.config.js"]
NextBuild --> TS["TypeScript_compilation_uses_tsconfig*.json"]
CSS --> Output["Optimized_CSS_and_assets_generated"]
TS --> Output
Output --> Deploy["Successful_Vercel_deployment_with_158_routes"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
gem-enterprise | 9166e01 | May 10 2026, 09:56 PM |
Vercel schema validation rejects the 'nodejs' key — it is not a valid vercel.json property. Node.js version is now specified via the 'engines' field in package.json instead, which Vercel reads automatically. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
Vercel schema requires env values to be plain strings, not objects with description/value properties. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes multiple issues blocking successful deployment to Vercel, discovered by auditing the repo config, CI workflows, and build pipeline.
Issues Found & Fixed in This PR
1.
.vercelignoreexcludes build-critical files (CRITICAL BLOCKER)postcss.config.js,tailwind.config.ts, andtsconfig*.jsonwere listed in.vercelignore, which prevents them from being uploaded to Vercel during deployment. These files are required duringnext build— without them, Tailwind CSS processing fails and TypeScript compilation breaks. Removed these exclusions.2.
.vercelignorewrong eslint config filenameListed
eslint.config.jsbut the actual file iseslint.config.mjs. Fixed to match.3.
AGENTS.mdreferencesnext.config.tsbut file isnext.config.jsAgent docs pointed to a
.tsfile that doesn't exist, causing confusion for automated agents.4.
VERCEL_DEPLOYMENT_GUIDE.mdusesnpminstead ofpnpmProject mandates pnpm exclusively. Guide had
npm install -g vercel,npx vercel, andnpm run build. Replaced with pnpm equivalents.5.
.gitignorecomment says "use npm only"Misleading comment corrected to reference pnpm.
Issues Found That Require Manual Fix (workflow scope needed)
6. Guardian workflow (
.github/workflows/main.yml) — CRITICAL CI BLOCKERThis workflow fails on every PR due to multiple issues. I couldn't push this fix because the OAuth token lacks
workflowscope. You need to apply these changes manually via the GitHub web editor or with a PAT that hasworkflowscope:test -f next.config.ts→ The file isnext.config.js. This assertion fails and blocks the entire workflow.branches:key — YAML silently drops the first value.NEXT_PUBLIC_SUPABASE_URL,VITE_SUPABASE_*) that no longer exist in the project. Should usePOSTGRES_PRISMA_URLandPOSTGRES_URL_NON_POOLING.DATABASE_URLbut Prisma usesPOSTGRES_PRISMA_URL.pnpm run buildruns without required env vars — needs fallback values.Additional Observations (No Code Change Needed)
vercel.jsonis correctly configured withpnpm run db:generate && pnpm run build.POSTGRES_PRISMA_URL,POSTGRES_URL_NON_POOLING,JWT_SECRET, andNEXT_PUBLIC_APP_URLare set in Vercel Project Settings.src/middleware.ts: CLAUDE.md references auth middleware for/app/*routes, but no middleware file exists. Unauthenticated users are not auto-redirected to login. This is a functional gap but not a build blocker.Review & Testing Checklist for Human
.github/workflows/main.ymlvia GitHub web UI to changenext.config.ts→next.config.js, fix the duplicate branches key, and update env vars (see details above)POSTGRES_PRISMA_URL,POSTGRES_URL_NON_POOLING,JWT_SECRET,NEXT_PUBLIC_APP_URL, andNEXT_PUBLIC_APP_NAMEare configured in Vercel Dashboard → Project → Settings → Environment Variables.vercelignoreVERCEL_TROUBLESHOOTING.md, ensure the proxy status for your Vercel CNAME is set to "DNS Only" (grey cloud) to avoid Error 1000Notes
The
.vercelignoreexcludingtailwind.config.ts,postcss.config.js, andtsconfig*.jsonwas likely the primary reason Vercel builds were failing — these files are essential for the Next.js build pipeline but were being stripped before the build ran on Vercel's infrastructure.Link to Devin session: https://app.devin.ai/sessions/8f3d4b175dd245dd9d4382b79083dac7
Requested by: @support371
Summary by Sourcery
Align Vercel deployment configuration and project documentation with the actual build tooling and file layout to unblock deployments.
Bug Fixes:
Enhancements: