[HELP] Trying to init a shadcn/ui project, but it keeps trying to access a random folder and fails.

[mmmmaaaaarrrrrrkkkkkkkk]

I don't see what I'm doing wrong. I open CMD as Administrator in the folder C:\Users\Administrator\Documents\project, and then I run npx shadcn@latest init.

The process goes smoothly, until it asks for my base color choice. After selecting a color, it immediately fails because it's trying to access C:\Users\Administrator\Documents\My Music which is a completely random and nonexistent folder and it's outside of the directory I'm running from.

Here's a copy-paste from the command line if that helps any:

C:\Users\Administrator\Documents\project>npx shadcn@latest init
√ The path C:\Users\Administrator\Documents\project does not contain a package.json file.
  Would you like to start a new project? » Next.js
√ What is your project named? ... project
√ Creating a new Next.js project.
√ Which color would you like to use as the base color? » Zinc
√ Writing components.json.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

EPERM: operation not permitted, scandir 'C:\Users\Administrator\Documents\My Music'

Thanks in advance!

[mmmmaaaaarrrrrrkkkkkkkk]

It looks like the My Music folder DOES exist, it's just one of those absolutely wonderful hidden OneDrive folders. It doesn't even show when you tick on "Show hidden files". I had to delete the My Music folder, as well as any other "My" folders via the command line.

I retried the installation, and everything worked fine. I hate Windows...

At least this is here for anyone running into the same problem.

[joshpachner]

Yeah Windows is weird.
Randomly I started to get this error.
I resolved it by just putting my project within another folder. So that it wasnt C:\users\me\Documents\project
but instead
C:\users\me\Documnets\nested_folder\project

[rif-enriquez]

worked for me too

[rif-enriquez]

this is actually crazy.. why is the init command looking for access anywhere outside its current directory at all?

[johnzenith]

It's not actually accessing anywhere outside, it's related with the installation package in node_modules folder. I don't want to say deadlock situation, but it looks more like it. If you close everywhere where that folder is opened, and run the installation again it should work fine.

[johnzenith]

On windows, this may happen. It is related with the running process (it's just like, hey, this folder/program is currently being used by a running process).

So close the folder, your coding editor and terminal where that path is accessed.
Open a new terminal and re-run the installation command, it should fix it.