Closed yoshi6jp closed 8 years ago
Hi, I ran into this issue as well. Problem is, this depends on your version of npm. On npm 2, which ships with node 4, (current LTS), the path will work as it is currently resolved. On npm 3 however, shipping with node 5, the new behavior is to flatten the dependency tree, causing the .cmd to go in a top-level .bin. Means there is probably a check to be made to correctly resolve the dependency according to the environment, though this feels a bit hacky :/
This has already been fixed.
It is an error in the windows environment.
Fixed path for
wdio.cmd
.