-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[bug]: NextJS Monorepo install failing #7160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Have you tried to run canary instead?
For me it worked with pnpm
|
@vsDizzy Whoops that was a typo in the above. I was using To me what it looks like is happening is it setting pnpn workspaces for npm workspaces. |
The current Monorepo template only supports "pnpm". "npm" and "bun" fail. |
The current monorepo template uses Turbo Repo. They already have a lot of examples https://github.com/vercel/turborepo/tree/main/examples which get "transformed" into the package managers ecosystem: https://github.com/vercel/turborepo/blob/0bba6fd60152869876061ce3fbd653a12d8649ff/packages/create-turbo/src/transforms/package-manager.ts#L13. I believe a similar transformation step is just missing here. There actually was a PR for shadcn, which got rejected. Maybe there is way to use the tranformation tools from turbo repo... ? |
please, upgrade turbo in shadcn@2.6.0-canary.2 "turbo": "^2.4.2", to "turbo": "^2.5.2", |
Describe the bug
When running
npx shadcn@canary init
and selectingNext.js (Monorepo)
I get the following errorAffected component/components
The initial installation
How to reproduce
npx shadcn@latest init
Next.js (Monorepo)
Codesandbox/StackBlitz link
No response
Logs
System Info
Before submitting
The text was updated successfully, but these errors were encountered: