I agree with updating in small steps. So, don't back off on this, just check if anything breaks, then do it!
-Michal On Tue, Oct 22, 2013 at 10:28 AM, Carlos Santana <[email protected]>wrote: > Michal, > Just to push to latest version. > > In my opinion is good to update dependencies in small steps, vs going with > an old dependency for a long time and then doing major jump. > (What's the cordova community opinion? regards on updating npm dependencies > for cli/plugman) > > jasmine-node 1.11.1 support jasmine 1.3.11 (latest GA) > > From comparing releases/tags history on both jasmine and jasmine-node, it > looks like jasmine-node picks up latest jasmine version pretty quickly. > > It's a minor thing anyway, I will leave it at 1.8.x then. > > --Carlos > > > > > > On Tue, Oct 22, 2013 at 9:25 AM, Michal Mocny <[email protected]> wrote: > > > I have no objection, but am curious what the motivation for upgrade is? > > Just pushing to latest version, or is there some feature you want (I ask > > because I'm evaluating jasmine-2.x and I'm curious about the direction > > jasmine-node seems to be going). > > > > -Michal > > > > > > On Mon, Oct 21, 2013 at 10:35 PM, Carlos Santana <[email protected] > > >wrote: > > > > > I notice that there is a new version of jasmine-node 1.11.0 [1] > > > > > > I tested with 1.11.0 today and didn't find problems at the surface. > > > > > > It is OK to update the dependency to use the new version? > > > > > > [1] https://npmjs.org/package/jasmine-node > > > > > > -- > > > Carlos Santana > > > <[email protected]> > > > > > > > > > -- > Carlos Santana > <[email protected]> >
