-
-
Notifications
You must be signed in to change notification settings - Fork 483
Open
Labels
cliThe issue relates to the CLIThe issue relates to the CLI
Description
Describe the bug
When I initialize shadcn in my project, normally I don't use the standard paths that the CLI provides. In this case, I've used a different one for the Shadcn utils file.
At the end of the process, the CLI shows where the utils file were placed, but, even thought it was placed in the correct path, it says that it was placed in the default path (src/lib/utils).
NOTE: I am willing to open a PR to address this issue
Reproduction
I've just tried to initialize Shadcn and noticed this bug. You can see the step by step process in the screenshot below:
Logs
System Info
System:
OS: Linux 6.12 Manjaro Linux
CPU: (12) x64 AMD Ryzen 5 5600G with Radeon Graphics
Memory: 8.55 GB / 13.52 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 22.16.0 - ~/.nvm/versions/node/v22.16.0/bin/node
npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm
pnpm: 10.12.4 - ~/.local/share/pnpm/pnpm
npmPackages:
@lucide/svelte: ^0.544.0 => 0.544.0
@sveltejs/kit: ^2.22.0 => 2.43.5
svelte: ^5.0.0 => 5.39.6
tailwindcss: ^4.0.0 => 4.1.13Severity
annoyance
Copilot
Metadata
Metadata
Assignees
Labels
cliThe issue relates to the CLIThe issue relates to the CLI