Windows cmd shim seems off

[butlersrepos]

Windows CMD shims are incorrect	The symlinking process appears to cmd shims the cmd shims, creating foo.cmd.cmd in the nested projects' node_modules/.bin
Version	0.19.3
Type	Issue
Node	8.11.1
OS	Windows 7
Short Desc	The cmd shims built into the projects' node module bin area do not work as expected.
Detailed Desc	Running a bare bolt command on my bolt project seems to set all deps up correctly however when creating the cmd shims in each projects' node_module/.bin there seem to be two created, the original foo.cmd and an additional foo.cmd.cmd. The npm scripts within my subprojects will try to invoke the former cmd shim and fail on The system cannot find the path specified from the shims first line "$basedir/../../../../node_modules/.bin/react-scripts.cmd" however if I manually invoke the foo.cmd.cmd that executable works as expected.

Difference between two cmd shims found in the same project's node_modules/.bin

[lukebatchelor]

Hiya,

We don't do any testing on windows machines here, the windows support was added by the community. Would you mind looking at the cause and creating a pr?

Also, is it possible some of those were there before you ran bolt? Could you try deleting your node modules and trying.

Lastly, @MarshallOfSound (I'll tag him properly when I get to a computer) might be able to give some insight here.

[butlersrepos]

Hey @lukebatchelor I did try nuking the .bin of the "sub" project in question to make sure that bolt was generating them and it was :(

...3 minutes later...

I just went to try it again using basic windows cmd, because I had been using Cmder before, and I do NOT observe the problem anymore 🤦‍♂️ So sorry about that. Ignore me.