-
Notifications
You must be signed in to change notification settings - Fork 2k
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
npm run dev -> EACCES: permission denied, open '/.config/postcssrc' #414
Comments
We don't do anything custom with postcss, this sounds like an upstream issue with Vue's CLI service, or something specific to your local installation/config of Node and your system. |
Thanks for the prompt response. I've bisected it to 895d448. That's where the |
I've also tried |
I had the similar error in a project and could fix either by disable the automatic configuration of the postcss loader in the webpack config file (in my case the
or by creating a simple postcss configuraton file in the project root directory
|
Nice one @jonaswjs :^) |
When your system is Linux, and your code is on a disk with an NTFS partition, you may encounter this issue, which can be resolved using the method provided by @jonaswjs 。 Possibly, adding support for ntfs-3g could also solve the problem? |
1 similar comment
When your system is Linux, and your code is on a disk with an NTFS partition, you may encounter this issue, which can be resolved using the method provided by @jonaswjs 。 Possibly, adding support for ntfs-3g could also solve the problem? |
Information
node=16.9.0
fromnodesource
onDebian 11
;npm=8.19.3
Help request
Problem
vue-cli-service serve src/nginxconfig/mount.js
, called fromnpm run dev
, tries to write to/.config/...
, and from there on everything breaks.Note that I'm not requesting an NPM global install or anything like that.
What I have tried
I've tried to check if there's some missing path configuration (i.e. some
DIR=''
variable would explain the attempted acccess to$DIR/.config/...
resolving to/.config/...
). I couldn't find it.The text was updated successfully, but these errors were encountered: