⌘K
Craiguito I’d isolate the database package before blaming Vercel or the whole template. From a clean folder, try the init with pinned tooling instead of all latest versions: corepack enable corepack prepare pnpm@9.15.4 --activate npx next-forge@latest init If it still creates the repo but fails at @repo/database, cd into the generated project and run: pnpm --filter @repo/database build That should give you the real TypeScript/ORM error instead of Turbo’s wrapper error. The log in the post only says the package build failed, not why. My guess is a version mismatch between the template’s database package
Ryu Hi Segal, The log you posted is still Turbo’s wrapper error, not the actual database package error. I’d isolate @repo/database first before treating the whole template as broken. From a clean terminal, try pinning the toolchain instead of using whatever “latest” resolves to: node -v corepack enable corepack prepare pnpm@9.15.4 --activate pnpm -v npx next-forge@latest init If the init still fails but leaves a partial repo behind, go into that repo and run the failing package directly: pnpm --filter @repo/database build or: cd packages/database pnpm build That should show the real TypeScript / O
system Thanks for reaching out! I've flagged this as high priority and connected you with @jacobparis who will assist you shortly.
Vsidera I have this same issue. How can I get past it ?
ADALIGO This usually happens when Vercel loses the GitHub connection permissions for the repo or branch. Try: Reconnect GitHub in Vercel settings Check if the repo still has PR permissions enabled Refresh the Git integration Make sure the branch protection rules are not blocking merges I had something similar before and reconnecting the GitHub app fixed it 👍
Anshuman Bhardwaj Hi @parenthesesweb1-2378, welcome to the Vercel Community! Are you talking about v0 here or the Vercel platform? Can you share when was the last commit you pushed to the main branch? Is the person committing and pushing to GitHub part of your Vercel team?
Gil Seeing the same issue. Github has the latest commit (verified) and manually redeployed on Vercel but it doesn’t seem to pick up the latest version.
Gil fixed it! the problem was that my email for commits was different than my email for Vercel. Here’s how I fixed it: set the email for git for the project (this is from the project folder): git config user.email "your-vercel-email@example.com" then create an ‘empty’ commit because nothing has really changed: git commit --allow-empty -m "Force Vercel redeploy" and push it: git push origin main that did the trick
Pauline P. Narvas Hey, @suheb! Feel free to share more details about your project, it'd help us tailor our suggestions, but some ideas to get you started: Bundle Size Optimization Use <@next> /bundle-analyzer to identify large dependencies: ANALYZE=true npm run build Enable optimizePackageImports in next.config.js for icon/utility libraries Implement code splitting and lazy loading for non-critical components Tree-shake unused code and remove unnecessary dependencies Image Optimization Use Next.js <Image> component for automatic optimization Images are served in modern formats (WebP/AVIF) reducing size by 25-35
Ryu A good way to approach this is to separate build/deployment size from runtime loading performance. For deployment/build size: Remove unused dependencies. Check for large assets accidentally included in the repo. Avoid bundling server-only packages into client components. Use dynamic imports for heavy UI/client-only code. Keep generated files, uploads, and local cache folders out of the deployment. For page performance: Use next/image for images. Compress large images before uploading them. Lazy-load below-the-fold components where it makes sense. Check bundle size with a bundle analyzer. Use V
Pauline P. Narvas It sounds like there is no Next.js version in your package.json file. Can you check for this? "next": "15.0.2" How did you do this? 🙂
Ryu Hi, That error usually means Vercel cannot find the package.json that contains next, or the project root is set incorrectly. A few things to check: In your repo, confirm next is listed in dependencies or devDependencies in the same package.json Vercel is building from. In Vercel, open Project Settings -> General -> Root Directory and make sure it points to the folder that contains that package.json. If this is a monorepo, set the root directory to the actual app folder, for example apps/web. Make sure the repo includes the lockfile from the same package manager you are using. Redeploy after ch
