-
Notifications
You must be signed in to change notification settings - Fork 56
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
Dependency on non-existing sh.exe #248
Comments
This is strange. This code is generated by NPM when you install the module. I'm developing on mac so I'm not running into the problem but I'll take a look in my windows vm. |
I tried on windows: My What are your node and npm versions? ( |
That was with node 0.10.17 and npm 1.3.8. I tried updating to the latest release package node 0.10.33 and npm 1.4.28. the generated script is slightly different, but the issue is exactly the same:
It seems to work as intended if I just replace the lot with:
So at least I can get rolling. A quick guess about the cause is that npm automatically identify streamline\bin_node as a shell script, which, to be fair, isn't technically wrong. Solving your issues with polyglots isn't exactly ideal in the first place.
Edit: Never mind about that last question, you have that covered in the API documentation. |
The polyglot solves #158 and #167. It allows smooth operation on linux and mac. But it does not work any more in windows command prompt because of the way npm generates its wrapper. I want to keep the polyglot for linux and mac so I'm going to investigate if there is a way to let npm install a custom script for windows, instead of letting it generate a broken wrapper. If someone knows a way I'm interested. Another easy fix would be to have a different command name for windows. Something like The |
The magic happens in https://github.com/ForbesLindesay/cmd-shim, which unfortunately seems to be locked hard to launch with whatever is specified in the shebang. |
I'm trying to run Streamline on Windows, but I have had no luck so far. _node seems to register correctly as a global command, but the contents of the corresponding _node.cmd file makes no sense:
Neither %~dp0/bin/sh.exe nor /bin/sh exist, and I don't see why anyone would assume that they did.
The text was updated successfully, but these errors were encountered: