-
Notifications
You must be signed in to change notification settings - Fork 552
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
node.js and npm #157
Comments
The node team officially stopped supporting cygwin after 0.4.12. |
Ohh, same problem for me. I was SO happy with babun until I had to resume some projects using node.js (gulp, bower, etc). |
Sry for post, I saw this ticket: #106 thats why I deleted my post. |
My problem is the same as here: nodejs/node-v0.x-archive#5618 my version of node is 0.10.17 and I really want to use node inside babun. I implemented babun inside ConEmu with help of the FAQ and maybe it's a problem with the parameters(?). When I create a new console and type this: "C:\Users\chrl.babun\cygwin\bin\bash.exe --login -i" I got an ugly black babun shell with a blue color for the dir and red arrows and when I type node, there is no problem only when I do it via the FAQ. Regards Chris |
An alternative solution is to use Winpty and create an alias.
|
Thought I'd share the answer given by stack-overflow user, troy, at http://stackoverflow.com/questions/10043177/node-js-cygwin-not-supported With admin rights, run That solves many issues, then if you continue to get EINVAL, this can usually be resolved by running a command in the native cygwin shell
|
@jlupi does it work for you now? |
It's not ideal, but you can do this with a virtual machine using Vagrant. Check out this vagrant box I've been using: |
@elebeaup I could kiss you, that works perfectly. |
@warrenfalk I read about dos2unix elsewhere and yes, that works for me. Thanks |
Hello
I am so far loving babun. With some initial setup errors, I finally got it working.
There are still some kinks here and there and I am trying to fix them one at a time.
I have some problems with both node.js and npm. both of which are failing.
Quick searches reveal something about node.js not working with cygwin..
Any thoughts?
This could be a dealbreaker for me, as I have some important developer tools running node.js
The text was updated successfully, but these errors were encountered: