Cool. I think for 0.7
With 0.7.1 this is fixed and required 0.10.25

See: [107.170.79.127] Meteor requires Node v0.10.25 or later.


On Fri, Feb 28, 2014 at 1:55 AM, steeve cannon <notifications@github.com>wrote:

> In example/mup.json:
>
> >    "setupMongo": true,
> > +
> > +  //WARNING: Nodejs is required! Only skip if you already have nodejs installed on server.
> > +  "setupNode": true,
> > +
> > +  //WARNING: If nodeVersion omitted will setup 0.10.24 by default. Do not use v, only version number.
>
> I thought latest compatible for Meteor was 0.10.24? The reason I thought
> that is because MUP before this PR produces this stoudput.
>
> This version of Meteor contains a patch for a bug in Node v0.10.
> The patch is against only versions 0.10.22 through 0.10.24.
> You are using version v0.10.26 instead, so we cannot apply the patch.
> To mitigate the most common effect of the bug, websockets will be disabled.
> To enable websockets, use Node v0.10.22 through v0.10.24, or upgrade to a later version of Meteor (if available).
>
> 0.10.25 is fine with me. I am going to set it in the mup.json depending on
> the meteor version and use case (testing vs. prod).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/arunoda/meteor-up/pull/29/files#r10140781>
> .
>



-- 
Arunoda Susiripala

@arunoda <http://twitter.com/arunoda>
<http://gplus.to/arunoda>https://github.com/arunoda
http://www.linkedin.com/in/arunoda