This repository has been archived by the owner on Aug 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 76
"no such file or directory" Doesn't Show Errant File/Directory Path #32
Comments
machineghost
changed the title
"no such file or directory" Doesn't Show Errant File/Directory
"no such file or directory" Doesn't Show Errant File/Directory Path
Dec 15, 2016
Thanks for your bug report. Would you be interested in filing a PR? |
This seems like a quick fix for someone who is already knows the library, but I know nothing at all about it (I'm only using it as part of a co-workers setup). So while I'm happy to submit PRs in general, the odds of me learning your code well enough to submit one anytime soon are pretty slim. Sorry. |
Not sure what the best approach would have been but I submitted my PR and ready for review 🙇 |
mc-zone
added a commit
to mc-zone/memory-fs
that referenced
this issue
May 30, 2017
1. Add path and operation name into error message, make it easier to figure out. 2. Change first line of stack to use correct message, instance of [object Object].
mc-zone
added a commit
to mc-zone/memory-fs
that referenced
this issue
May 30, 2017
1. Add path and operation name into error message, make it easier to figure out. 2. Change first line of stack to use correct message, instance of [object Object].
sokra
added a commit
that referenced
this issue
Jun 18, 2017
Prettify Error message and stack display, fix #32 .
same error ... somebody help ... |
I had the same issue and after I removed yarn.lock file and install modules again fixed it |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just got the following error from memory-fs:
As you can see, there's no mention of the path it was trying to use to find a file/directory. However, when I looked at the code it was clear that it intended to share that path:
and indeed, if I added a console .log ...
it logged the path successfully. So evidently there's something wrong with
MemoryFileSystemError
which is causing it to ignore or discard it's second argument.The text was updated successfully, but these errors were encountered: