Getting a `ENOENT: no such file or directory`
See original GitHub issueI’m decompressing a folder of files, I’m attempting to write them to dist
folder but getting a ENOENT: no such file or directory
error. Is this the normal behavior? If so, how does this library handle decompressing something like this?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:5
Top Results From Across the Web
node.js - ENOENT, no such file or directory - Stack Overflow
First try npm install ,if the issue is not yet fixed try the following one after the other. · npm cache clean ,then...
Read more >ENOENT: no such file or directory · Issue #1171 - GitHub
After updating from 6.3.0 to 6.4.1 I've got errors. node:internal/process/promises:246 triggerUncaughtException(err, true /* fromPromise */) ...
Read more >ENOENT: no such file or directory - Power Platform Community
I get the error: C:\Users\nuno_\Documents\NumberButtonSelector>npm run build npm ... verbose stack Error: ENOENT: no such file or directory, ...
Read more >ENOENT No Such File or Directory Open - YouTube
In This Video We Will See How to Fix npm ERR Code ENOENT npm ERR syscall Open Error or ENOENT No Such File...
Read more >ENOENT: no such file or directory ... but there is - Reddit
I'm having an issue similar to this person's (but it's hard to tell because they deleted their post). ... The error message I...
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 FreeTop 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
Top GitHub Comments
I got an
ENOENT: no such file or directory
error whenfile.type
was set tofile
rather thandirectory
for an entry namedimages/
(possibly because the entry didn’t have the appropriate external attributes).This workaround has been successful:
I was getting this and the originating error syscall was “link” and after looking on here it appears it doesn’t handle symlinks well. The workaround is to use the filter option. https://github.com/kevva/decompress/issues/52
decompress(inputpath, outputpath, { "filter": file => { if (file.type !== "link") { return true; } return false; } }) .then(files => { ... })