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 and current pnpm/turbo/Node. If the package builds after pinning pnpm and Node 20, it’s a template/tooling drift issue. If it still fails, the exact error from packages/database is the part to chase.

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:

1
node -v
2
corepack enable
3
corepack prepare pnpm@9.15.4 --activate
4
pnpm -v
5
npx next-forge@latest init
6

If the init still fails but leaves a partial repo behind, go into that repo and run the failing package directly:

1
pnpm --filter @repo/database build
2

or:

1
cd packages/database
2
pnpm build
3

That should show the real TypeScript / ORM / env-var error instead of only:

1
@repo/database:build exited (1)
2

I’d also check the root package.json after scaffolding. In a Turborepo + pnpm workspace, the packageManager field and lockfile matter for reproducible installs:

1
{
2
  "packageManager": "pnpm@9.15.4"
3
}
4

Turborepo documents that field here:

https://turborepo.com/docs/getting-started/add-to-existing-repository#add-a-packagemanager-field-to-root-packagejson

If the package builds with Node 20 + pinned pnpm but fails with pnpm 10/latest, then this is probably template/tooling drift. If it still fails after pinning, the next useful thing to share is the first actual error from packages/database, not the Turbo summary.