Closed
Description
- Version:
v6.0.0 - Platform:
Windows 32 and 64 bit - Subsystem:
I've noticed a minor breaking change in either child_process.spawn
or path.resolve
(currently unclear), on Windows with Node 6. This issue appears to crop up when a Node script is execute from a SUBST
'd path.
The production steps are tricky so I have created a reproduction in a repo that runs its tests in AppVeyor.