[bug]: shadcn CLI fails with EPERM error when adding Magic UI components on Windows

[mohdanas86]

Describe the bug

When trying to add Magic UI components using the shadcn CLI on Windows, the command fails with an EPERM permission error related to scanning the "Application Data" directory.

This prevents installing components like @magicui/orbiting-circles or smooth-cursor via the CLI, even in a valid Next.js + Tailwind + shadcn/ui project.

The issue seems to be Windows-specific and related to filesystem permissions or how the CLI resolves user directories.

Affected component/components

• Orbiting Circles - Smooth Cursor - shadcn CLI integration for Magic UI components

How to reproduce

1. Create a Next.js project with Tailwind CSS and shadcn/ui configured

2. Open PowerShell on Windows

3. Run the following command inside the project directory:

   npx shadcn@latest add @magicui/orbiting-circles

4. Observe the error below

Codesandbox/StackBlitz link

No response

Logs

PS C:\Users\akwent\portfolio> npx shadcn@latest add @magicui/orbiting-circles

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\akwent\Application Data'

System Info

OS: Windows 11
Shell: PowerShell
Node.js: v18.x
npm: v9.x
Framework: Next.js
CSS: Tailwind CSS
UI: shadcn/ui

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues