⌘K
Eduardo Pavez Hi @amyegan, Any thoughts on this? Thanks!
Amy Egan Hey @epavez, sorry I missed your earlier post! For the database filter, I believe those are typically related to Vercel Marketplace integration options. I'd be happy to get you connected with the team if you want to explore adding Backblaze B2 to the marketplace. Just lmk if you're interested in that 😃 As for the full-stack deployment, it looks like you already configured Services in a vercel.json file to deploy everything in a single Vercel project. That's the right approach for all-in-one deployment. Let me ask the templates team if they have any other info or recommendations
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
