Some of you might find this podcast [1] interesting, straight from the horse's mouth
They discuss npm 2.x, opinions about semver, and modules using pre-release strings as production packages, shrinkwrap, etc.. [1]: http://javascriptjabber.com/127-jsj-changes-in-npm-land-with-forrest-norvell-rebecca-turner-ben-coe-and-isaac-z-schlueter On Mon, Sep 22, 2014 at 1:46 PM, Michal Mocny <mmo...@chromium.org> wrote: > 1. pretty cool to be mentioned! > 2. The post led me to find: > https://gist.github.com/othiym23/4ac31155da23962afd0e which is basically > a > monkey patch for the recently-discussed-on-list npm upgrade command. > > -Michal > > On Mon, Sep 22, 2014 at 12:46 PM, purplecabbage <purplecabb...@gmail.com> > wrote: > > > And a good read for Cordova contributors, as it discusses > > dependency/versioning issues, which bites us frequently too. > > > > Sent from my iPhone > > > > > On Sep 22, 2014, at 9:37 AM, Ray Camden <rayca...@adobe.com> wrote: > > > > > > Gotcha. So not an issue for end users of Cordova - but perhaps for > plugin > > > authors. > > > > > > > > >> On 9/22/14, 11:34 AM, "Ian Clelland" <iclell...@chromium.org> wrote: > > >> > > >> It shouldn't matter for users, but I have seen several issues in the > > past > > >> where using the wrong version of npm means that you can't publish > > modules > > >> or plugins. It's something to be aware of, at least. > > >> > > >>> On Mon, Sep 22, 2014 at 12:30 PM, Ray Camden <rayca...@adobe.com> > > wrote: > > >>> > > >>> Being lazy, but can you explain why it matters? Ie, is there a reason > > >>> *not* to just upgrade? I assume most folks would think, ³new version > of > > >>> npm, just update and don¹t worry about it² - but does it impact using > > >>> Cordova? > > >>> > > >>> > > >>>> On 9/22/14, 11:09 AM, "Carlos Santana" <csantan...@gmail.com> > wrote: > > >>>> > > >>>> NPM 2.x was released last week. > > > > > > -- Carlos Santana <csantan...@gmail.com>
