Error after installing with tailwindcss using vite #17590
Unanswered
zaib-shekh
asked this question in
Help
Replies: 1 comment
-
Hey! This indeed looks like a file permissions issue. However, Tailwind CSS itself doesn't try to remove any files or folders, especially not in the If you can create a minimal reproduction repo then we might be able to help. I did find an issue on the Vite repo itself, but it got closed because they couldn't reproduce it. Maybe you can help by providing more info: vitejs/vite#14056 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of Tailwind CSS are you using?
Using: v4.1
What build tool (or framework if it abstracts the build tool) are you using?
Using : Vite 6.1.0 + react
What version of Node.js are you using?
Using: v20.15.0
What browser are you using?
Using: Chrome, Brave
What operating system are you using?
Using: Windows
Reproduction URL
A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.
A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.
Describe your issue
I installed Tailwind CSS for my Vite + React project and followed all the necessary steps from the Tailwind CSS documentation. However, when I run the project, I get the following error:
Error: EPERM: operation not permitted, rmdir 'C:\Users\<User>\OneDrive\Desktop\<Project Name>\node_modules\.vite\deps'
I've tried several times, but I keep getting the same error. I suspect the issue might be related to OneDrive or file permission conflicts.
Beta Was this translation helpful? Give feedback.
All reactions