Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"utimes" doesn't work for directories: "EISDIR: illegal operation on a directory, open ..." error
See original GitHub issueutimes calls utimesBase which uses openSync call internally but openSync call on a directory obviously throws EISDIR error.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
NPM stuck giving the same error EISDIR: Illegal operation on ...
EISDIR stands for "Error, Is Directory". This means that NPM is trying to do something to a file but it is a directory....
Read more >eisdir: illegal operation on a directory - You.com
npm command - Error: EISDIR: illegal operation on a directory, read. First try to locate you npmrc file in your computer. Try this...
Read more >File System
Emitted when something changes in a watched directory or file. ... (err, fd) => { // => [Error: EISDIR: illegal operation on a...
Read more >sfdx cli throwing error "EISDIR: illegal operation on a directory ...
You should be able to fix this by changing the permissions of that folder to your user. Something like:
Read more >concept directory in category node - liveBook · Manning
fs.js:60 throw err; // Forgot a callback but don't know where? Use NODE_DEBUG=fs ^ Error: EISDIR: illegal operation on a directory, read at...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems related to https://github.com/streamich/memfs/issues/58. Maybe
ris too restrictive there? Modifying those lines seems to fix the issue for me.🎉 This issue has been resolved in version 3.4.9 🎉
The release is available on:
Your semantic-release bot 📦🚀