In general Ray for all npm pacakge authors and how they define their package.json dependencies, devDependencies, optionalDependencies, and lastly peerDependencies.
Cordova now publishes 12 npm packages. Also to take into account testing!, We need to make sure that end users using any version of npm 1.x or 2.x can still install our cordova packages. we currently don't test using npm@2.x duh! since it just got released. we need to make sure our cordova packages install correctly. On Mon, Sep 22, 2014 at 12:37 PM, 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>
