Skip to content
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

Open
davidjorgensen opened this issue May 27, 2014 · 10 comments
Open

node.js and npm #157

davidjorgensen opened this issue May 27, 2014 · 10 comments

Comments

@davidjorgensen
Copy link

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.

net.js:156
    this._handle.open(options.fd);
                 ^
Error: EINVAL, invalid argument
    at new Socket (net.js:156:18)
    at process.stdin (node.js:660:19)
    at startup (node.js:145:16)
    at node.js:902:3

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

@srijanshetty
Copy link
Contributor

The node team officially stopped supporting cygwin after 0.4.12.
Here's the wiki link https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-(Windows)

@sveggiani
Copy link

Ohh, same problem for me. I was SO happy with babun until I had to resume some projects using node.js (gulp, bower, etc).
Any chance to use replace cygwin? maybe msysGit?

@Chris2011
Copy link

Sry for post, I saw this ticket: #106 thats why I deleted my post.

@Chris2011
Copy link

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

@elebeaup
Copy link

An alternative solution is to use Winpty and create an alias.

$ alias node="console cmd /c node"
$ node
> console.log('Hello World')
Hello World

@warrenfalk
Copy link

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 dos2unix '/cygdrive/c/Program Files/nodejs/npm'

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

cygstart /bin/bash

@tombujok
Copy link
Contributor

tombujok commented Apr 4, 2015

@jlupi does it work for you now?

@TWGerard
Copy link

TWGerard commented Sep 8, 2015

It's not ideal, but you can do this with a virtual machine using Vagrant. Check out this vagrant box I've been using:

https://github.com/semmypurewal/node-dev-bootstrap

@lukecfairchild
Copy link

@elebeaup I could kiss you, that works perfectly.

@jorgeorpinel
Copy link

@warrenfalk I read about dos2unix elsewhere and yes, that works for me. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants