-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
recommend iojs #390
recommend iojs #390
Conversation
shit i forgot the bash command... |
nvm i don't know what i'm doing haha |
After I installed /usr/local/bin/node -> iojs Should we stick with Well, I have not tested in |
but the commands don't run with |
alias iojs='node --harmony-generators '
➜ which iojs
iojs: aliased to node --harmony-generators
➜ iojs xxx.js
node: bad option: --harmony-generators From The current behaviour of the I think the correct Bash command should be # put it in .bashrc, or .zshrc
alias iojs='node --harmony ' Test the command above ➜ which iojs
iojs: aliased to node --harmony
➜ iojs xxx.js
# run and log stdout... |
how do you only alias |
After some tests on this matter, I think this could be a solution. if [ ! -x "$(command -v iojs)" ]
then
alias iojs='node --harmony '
fi read more about |
typically you do |
i'd like tests to run without iojs users having to do |
why? there's only a few people that work on the tests, or we can default it to iojs instead |
yeah we can default to iojs |
one thing i'd like to wait for is for nvm/travis to support iojs and start testing on that. i could also push this now