-
Notifications
You must be signed in to change notification settings - Fork 218
EACCES: permission denied
when starting
#174
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
Hey @logikaljay. What do you think is the expected behaviour in this situation? |
If the extension can't read the directory, I would expect it to just be skipped. |
I also have this issue. My use case is that I use docker, and the containers store data in a "docker/.data" directory inside my project. It is a real pain to configure a docker container to write to shared volumes in a manner that is readable and writeable by the host user. "Hey @logikaljay. What do you think is the expected behaviour in this situation?" For me, I think the current behavior is fine. However, I would at least like the ability to exclude directories from being scanned as a setting. Most extensions have this kind of setting. Even if it could look up the "files.exclude" setting, that would work for me. |
I also have this issue because using docker volume in my project. I suggest that tailwind can use the .gitignore for starting point to exclude unwanted files. |
Going to close this as the original issue is resolved. With regards to excluding files let's track that over at #139 👍 |
The extension crashes on start when it doesn't have permission to a folder or file in the project.
Example:
The text was updated successfully, but these errors were encountered: