Re: cordova-js errors and coho
Yes, should be safe to remove the flag. On Thu, May 22, 2014 at 7:58 PM, Michal Mocny mmo...@chromium.org wrote: I just removed them locally and you are right, they are no longer needed. SGTM. On Thu, May 22, 2014 at 7:43 PM, Jesse purplecabb...@gmail.com wrote: coho has the --harmony-generators directly in the coho bash script [1], and the coho.cmd file. [2] On windows, I need to remove --harmony-generators from [1] if I am running from a git-bash terminal, and from [2] if I am running from cmd. Both break execution in node v0.10.22, so I would like to remove them so we can all run the same thing. Other than that, everything seems fine. [1] https://github.com/apache/cordova-coho/blob/master/coho#L1 [2] https://github.com/apache/cordova-coho/blob/master/coho.cmd#L1 @purplecabbage risingj.com On Thu, May 22, 2014 at 4:29 PM, Michal Mocny mmo...@chromium.org wrote: RE: gnode, Awesome. RE: --harmony-generators, not sure what you mean. Did you add that manually to your local node flags? I no longer need to do anything to my environment for coho to run, and I don't much care that coho uses magic from the future. -Michal On Thu, May 22, 2014 at 6:03 PM, Jesse purplecabb...@gmail.com wrote: gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I
Re: cordova-js errors and coho
Thanks, I was waiting for Andrew's approval. Issue #CB-6745, opened and closed @purplecabbage risingj.com On Fri, May 23, 2014 at 7:42 AM, Andrew Grieve agri...@chromium.org wrote: Yes, should be safe to remove the flag. On Thu, May 22, 2014 at 7:58 PM, Michal Mocny mmo...@chromium.org wrote: I just removed them locally and you are right, they are no longer needed. SGTM. On Thu, May 22, 2014 at 7:43 PM, Jesse purplecabb...@gmail.com wrote: coho has the --harmony-generators directly in the coho bash script [1], and the coho.cmd file. [2] On windows, I need to remove --harmony-generators from [1] if I am running from a git-bash terminal, and from [2] if I am running from cmd. Both break execution in node v0.10.22, so I would like to remove them so we can all run the same thing. Other than that, everything seems fine. [1] https://github.com/apache/cordova-coho/blob/master/coho#L1 [2] https://github.com/apache/cordova-coho/blob/master/coho.cmd#L1 @purplecabbage risingj.com On Thu, May 22, 2014 at 4:29 PM, Michal Mocny mmo...@chromium.org wrote: RE: gnode, Awesome. RE: --harmony-generators, not sure what you mean. Did you add that manually to your local node flags? I no longer need to do anything to my environment for coho to run, and I don't much care that coho uses magic from the future. -Michal On Thu, May 22, 2014 at 6:03 PM, Jesse purplecabb...@gmail.com wrote: gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote:
Re: cordova-js errors and coho
Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a
Re: cordova-js errors and coho
..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with
Re: cordova-js errors and coho
gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely
Re: cordova-js errors and coho
RE: gnode, Awesome. RE: --harmony-generators, not sure what you mean. Did you add that manually to your local node flags? I no longer need to do anything to my environment for coho to run, and I don't much care that coho uses magic from the future. -Michal On Thu, May 22, 2014 at 6:03 PM, Jesse purplecabb...@gmail.com wrote: gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey
Re: cordova-js errors and coho
coho has the --harmony-generators directly in the coho bash script [1], and the coho.cmd file. [2] On windows, I need to remove --harmony-generators from [1] if I am running from a git-bash terminal, and from [2] if I am running from cmd. Both break execution in node v0.10.22, so I would like to remove them so we can all run the same thing. Other than that, everything seems fine. [1] https://github.com/apache/cordova-coho/blob/master/coho#L1 [2] https://github.com/apache/cordova-coho/blob/master/coho.cmd#L1 @purplecabbage risingj.com On Thu, May 22, 2014 at 4:29 PM, Michal Mocny mmo...@chromium.org wrote: RE: gnode, Awesome. RE: --harmony-generators, not sure what you mean. Did you add that manually to your local node flags? I no longer need to do anything to my environment for coho to run, and I don't much care that coho uses magic from the future. -Michal On Thu, May 22, 2014 at 6:03 PM, Jesse purplecabb...@gmail.com wrote: gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with
Re: cordova-js errors and coho
I just removed them locally and you are right, they are no longer needed. SGTM. On Thu, May 22, 2014 at 7:43 PM, Jesse purplecabb...@gmail.com wrote: coho has the --harmony-generators directly in the coho bash script [1], and the coho.cmd file. [2] On windows, I need to remove --harmony-generators from [1] if I am running from a git-bash terminal, and from [2] if I am running from cmd. Both break execution in node v0.10.22, so I would like to remove them so we can all run the same thing. Other than that, everything seems fine. [1] https://github.com/apache/cordova-coho/blob/master/coho#L1 [2] https://github.com/apache/cordova-coho/blob/master/coho.cmd#L1 @purplecabbage risingj.com On Thu, May 22, 2014 at 4:29 PM, Michal Mocny mmo...@chromium.org wrote: RE: gnode, Awesome. RE: --harmony-generators, not sure what you mean. Did you add that manually to your local node flags? I no longer need to do anything to my environment for coho to run, and I don't much care that coho uses magic from the future. -Michal On Thu, May 22, 2014 at 6:03 PM, Jesse purplecabb...@gmail.com wrote: gnode seems good on windows Can I remove the --harmony-generators then? Or do I need to make a new root command? noho, windoho, woho, fauxho ? @purplecabbage risingj.com On Thu, May 22, 2014 at 2:47 PM, Michal Mocny mmo...@chromium.org wrote: ..but I haven't tested gnode on windows, sorry. On Thu, May 22, 2014 at 5:47 PM, Michal Mocny mmo...@chromium.org wrote: I no longer use node 0.11 and coho runs fine on 0.10 thanks to gnode. nvm/nave aren't necessary at all (I think), especially now that we don't need to switch node versions just for coho, they are just convenient if you want to jump around environments or lack permissions to do global installs. Yes, I think node 0.11 was needed for coroutines (function*()) and yield, I'm not sure if other es6 features were used. -Michal On Thu, May 22, 2014 at 5:28 PM, Jesse purplecabb...@gmail.com wrote: Reviving this thread ... ping! Is the only reason we depend on node v0.11 to support 'yield'? also: Has anyone managed to run this on windows? Not having good luck with nave or nvm @purplecabbage risingj.com On Thu, May 15, 2014 at 9:40 AM, Steven Gill stevengil...@gmail.com wrote: Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage
Re: cordova-js errors and coho
Yes, I agree it is much cleaner with everything broken out into modules. And I agree that we can be a bit more flexible as this is a tool that we use, and not a tool that our users use. Is the only reason we depend on node v0.11 to support 'yield'? Because I can live without that portion of the refactor ... seems very academic to me. @purplecabbage risingj.com On Tue, May 6, 2014 at 7:48 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Don't you guys just love these dropped emails :) On May 15, 2014 6:47 AM, Brian LeRoux b...@brian.io wrote: https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
https://github.com/TooTallNate/gnode/blob/master/README.md On May 7, 2014 1:18 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
OK, so here is the thing: We need to be able to be release. Having to use a particular dev version of node is unacceptable, especially since the tests don't work with the most recent version of the dev branch of node. (0.11.13) Saying it works on my machine is unacceptable as well, since you're probably running 0.11.12 and this quirk isn't documented anywhere. The question should be does it work on a clean machine using the current documentation. I deleted and re-cloned my cordova-js tree three to eliminate the possibly of it being anything in that repo. If we have to throw out coho because it's the right tool for the job, we should have that conversation after 3.5.0 is out. Can we fix this so that if we need to rush a 3.5.1 out for a platform that we're now slowed down by both our tools and our process? On May 7, 2014 1:09 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Heads up: I tried to publish an npm package with node 0.11 last week and it did not go well. Published without error, but then you couldn't install on node 0.10 without a checksum failure. Seems brittle/bug on the part of npm, but it does mean we should be very careful not to use 0.11 to publish releases. -Michal On Wed, May 7, 2014 at 4:33 PM, Jesse purplecabb...@gmail.com wrote: Yes, I agree it is much cleaner with everything broken out into modules. And I agree that we can be a bit more flexible as this is a tool that we use, and not a tool that our users use. Is the only reason we depend on node v0.11 to support 'yield'? Because I can live without that portion of the refactor ... seems very academic to me. @purplecabbage risingj.com On Tue, May 6, 2014 at 7:48 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Seems we have a happy ending here. Ran into this on the weekend: https://github.com/TooTallNate/gnode Added it in and now coho just works with v0.10 or v0.11 of node. It adds about 2 seconds of start-up latency for v0.10, but at least it works. On Mon, May 12, 2014 at 9:34 AM, Michal Mocny mmo...@chromium.org wrote: Heads up: I tried to publish an npm package with node 0.11 last week and it did not go well. Published without error, but then you couldn't install on node 0.10 without a checksum failure. Seems brittle/bug on the part of npm, but it does mean we should be very careful not to use 0.11 to publish releases. -Michal On Wed, May 7, 2014 at 4:33 PM, Jesse purplecabb...@gmail.com wrote: Yes, I agree it is much cleaner with everything broken out into modules. And I agree that we can be a bit more flexible as this is a tool that we use, and not a tool that our users use. Is the only reason we depend on node v0.11 to support 'yield'? Because I can live without that portion of the refactor ... seems very academic to me. @purplecabbage risingj.com On Tue, May 6, 2014 at 7:48 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I
Re: cordova-js errors and coho
One thing is for sure, the new coho is way better than the old coho. Fingers crossed for 0.12 On Tue, May 6, 2014 at 7:48 PM, Michal Mocny mmo...@chromium.org wrote: Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
I'd like to see platforms release process be more like plugins/tools in that it doesn't use a does-a-lot-of-stuff coho command. Feel free to write a new process. Possible that we could make coho work via traceur. Feel free to take a stab at it if you'd like. If things are failing with v0.11, we should probably fix them since they will likely be broken for v0.12. What's broken for you? *works on my machine*. On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Damnit. Perplexing choice. Coho isn't released to end users, and the codebase is tremendously cleaner and more maintainable now. On the other hand, doing release testing using development version of node does seem odd. One possible solution, for now, is nvm supports changing the version for a given terminal session only (nvm use). Can leave your default node to 0.10, and you can use a dedicated terminal for using coho. Longer term, I'm not sure. Hope node 0.12 ships soon? -Michal On Tue, May 6, 2014 at 7:15 PM, Anis KADRI anis.ka...@gmail.com wrote: I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
OK, so using 0.11.12 does work to get coho working. Does anyone other than me think that this is completely stupid? On Tue, May 6, 2014 at 3:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
Re: cordova-js errors and coho
I got excited and tried to use the latest version of coho but when I saw that it was using an odd version I just gave up. On Tue, May 6, 2014 at 4:11 PM, Steven Gill stevengil...@gmail.com wrote: Thanks for sharing Martin! I also am on the train that we shouldn't be using unstable versions of node. I don't know if the landscape has changed since I started using node, but I was always taught to stick to even version numbers. On Tue, May 6, 2014 at 4:03 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: Agree guys we shouldn't be depending on unstable node versions to work, just sharing what it worked for me. I think coho has been using node 0.11 since the last clean up a few days ago. Hey Joe, I've just shared with you my findings, it's not the best solution I know that, but it worked for me. On May 6, 2014 5:47 PM, Jesse purplecabb...@gmail.com wrote: We shouldn't be depending on unstable versions of node, imo. Being able to switch versions is not a solution. @purplecabbage risingj.com On Tue, May 6, 2014 at 3:40 PM, Martin Gonzalez Glez martin.c.glez.g...@gmail.com wrote: I had the same problem with nodejs 0.11, using url.parse module and running the Unit Test on cordova-js, those are failing with nodejs 0.11.13, but with 0.11.12 it works fine. Nodejs 0.11 it's working unestable, they are going to release one more 11.xx version before nodejs 0.12 (According to their google group forum). It seems that cordova-coho uses a dependency that requires node 0.11. A quick fix in your case Joe it's the usage of a node version manager as n or nvm for Mac OS X, or nodist under Windows. It won't fix your nodejs 11, but it allows you to switch between nodejs versions easily and quickly. On May 6, 2014 5:07 PM, Joe Bowser bows...@gmail.com wrote: Hey I know that for some reason, we decided to use node 0.11 for coho, but the thing is that it means that we can't run the Unit Tests on cordova-js now. At least on my machine, coho will now always fail because of either named branch errors or Unit Test errors. This seems to be some weird unicode enforcing that is happening in the node 0.11. This is extremely frustrating, since we're supposed to use this coho tool to do releases to automate the process, yet the tool keeps breaking every time we try and use it. I'm sure that there's a whole other thread where this issue was beaten to death, but I didn't need to try to tag an RC1 for 3.5 when that was happening. Seriously, can we make coho work with stable node versions, or agree to stop using it altogether and re-write the docs on cutting a release? I probably will have to do RC1 manually because of how broken it is right now.
