cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gonzalez Glez <martin.c.glez.g...@gmail.com>
Subject Re: cordova-js errors and coho
Date Tue, 06 May 2014 23:03:55 GMT
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" <purplecabbage@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.glez@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" <bowserj@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.
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message