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
Error: EPERM: operation not permitted, lstat (gatsby-starter-default + gatsby-source-wordpress) #16353
Comments
Hi @mavalon! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it. I can't seem to reproduce this on my own. If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look. Thanks for using Gatsby! 💜 |
I ended up switching to |
Happened to me while my VScode was Open so i closed it and used to run gatsby develop on cmd and it worked . |
I had same issue this worked for me just type |
Really annoying to have to |
I can't even run gatsby clean anymore, as the same error is happening there too! |
This still happens very often. I am on Windows 11 using the new Powershell. Seems like it has something to do with Windows permissions. |
Have you found a solution to this? I'm also using Windows 11. I've tried closing VS code and running gatsby develop but to no avail. |
Running into this as well, possibly linked to hot reload working inconsistently (needs a restart). |
this issue still exists, win11 |
this solved it for me https://nextjs.org/ 🤣 |
Description
I installed the default starter and the wordpress plugin. Running
develop
compiles successfully. But, a few seconds later an error is thrown.Steps to reproduce
gatsby-starter-default
gatsby-source-wordpress
gatsby develop
Expected result
Actual result
Environment
Additional info
Also, I notice that immediately after it says that it compiled successfully, I can see image files in the
.cache/gatsby-source-filesystem
directory. But, a few moments later, when the error above occurs and the server is stopped, all the files disappear. (Perhaps it's normal to remove the files when the server stops, but I thought I'd mention that here, just in case it's not.)Also, if I comment out the
media
path ingatsby-config
for the wordpress plugin configuration section, then I get no errors:The text was updated successfully, but these errors were encountered: