Tianen Pang check this one github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix
ADALIGO The error comes from tooling mismatch not from you Luknuts56, just downgrade ESLint and you’re good 👍
Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your loading.tsx file. Your package.json has: and the stack trace is failing inside eslint-plugin-react while loading the react/display-name rule. There’s an open Next.js issue for this same ESLint 10 error: github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: If it still keeps ESLint 10 because of the lockfile, do a clean install: One more thing: since you’re following a course, I’d avoid using "latest" for next, react, and react-dom. The tutorial may have been writ
Anshuman Bhardwaj Hi @shige, thanks for taking the initiative for this with a PR. I'll share it with our team. If you are confident about the PR feel free to make it ready so maintainers can review.
Tadashi Shigeoka Thanks, @anshumanb san! I’ve marked the PR as ready for review. Looking forward to the team’s feedback.
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: If the init still fails but leaves a partial repo behind, go into that repo and run the failing package directly: or: That should show the real TypeScript / ORM / env-var error instead of only: I’d also check the root package.json after scaffolding. In a Turborepo + pnpm workspace, the packageManager field and lockfile mat