-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
fs.statSync does not throw an error when accessing non-existent directory on Windows 10 #9106
Comments
Can't reproduce. Can you provide an example of path_to_missing_dir? |
The path which I was trying to reach when I came across this problem was |
Are you sure that directory actually doesn't exist and isn't just hidden? |
Positive it doesn't exist, but I did just try this on another system and can't reproduce... so since I am using nvm-windows to install node, I just upgraded my system to v6.8.0, and the error was properly thrown. |
OK, reinstalled 6.7.0 on my system and the error is properly thrown now as well. Possibly something was corrupted with my original installation of 6.7.0. Looks like this was a non-issue and can be closed. |
On Windows 10, I am not getting the same behavior of fs.statSync when trying to access a non-existent directory as I do on Linux. The expected result is for an error to be thrown, which occurs on Linux, but not on Windows 10.
Example:
The text was updated successfully, but these errors were encountered: