-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Description
- Version: any
- Platform: windows x64
- Subsystem: runtime
Made a script for cleaning up disk and unlocking locked files. The script is written in JavaScript and intended to be run using Node.js in Windows safe mode.
When run the script in windows normal mode, it works. However, when run the script in windows safe mode, get the error:
socket: (10050) A socket operation encountered a dead network
After googling found out that windows safe mode disables network drivers and Node.js won't start if network drivers are disabled.
Is there a reason to terminate Node.js if there are no network drivers enabled? The script is supposed to use only fs and path module in order to unlink some files and rmdir directories. Network is really irrelevant and terminating the Node.js process because of missing drivers doesn't really make sense to me.
But, this is total guess, I'm not sure if missing drivers cause it or whatever, that's what I found on google and stack overflow.
To make it clear: the feature request is to allow Node.js to run in windows safe mode, without requiring any irrelevant configuration to be present (like network drivers, if that is the cause). Would like to hear your opinion.