Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of iclelland@google.com designates
 209.85.218.46 as permitted sender)
MIME-Version: 1.0
Sender: iclelland@google.com
In-Reply-To: <D045B8C2.139B0%raycamde@adobe.com>
References: 
 <CAHYtTqkEDfXnJHAQmp9KRPPPKaH+_Rkp4Y8VpTcUrDCA6p0x8w@mail.gmail.com>
 <D045B8C2.139B0%raycamde@adobe.com>
From: Ian Clelland <iclelland@chromium.org>
Date: Mon, 22 Sep 2014 12:34:53 -0400
Message-ID: 
 <CAK_TSXK9EG_E-0i-+rw5pTegtjPQDKgho-sZXJFbpOQyCiQUPQ@mail.gmail.com>
Subject: Re: new NPM 2.x
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7bd6c6e002c8610503aa0972

--047d7bd6c6e002c8610503aa0972
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 <raycamde@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, =C2=B3new version=
 of
> npm, just update and don=C2=B9t worry about it=C2=B2 - but does it impact=
 using
> Cordova?
>
>
> On 9/22/14, 11:09 AM, "Carlos Santana" <csantana23@gmail.com> wrote:
>
> >NPM 2.x was released last week.
> >
> >latest nodejs stable 0.10.32 comes with npm@1.4.28
> >
> >if you do $ npm install -g npm  (you will get npm@2.0.0)
> >
> >More about npm 2.x and semver:
> >http://blog.npmjs.org/post/98131109725/npm-2-0-0
> >
> >cordova and phonegap get's mentioned in the blog post.
> >
> >For now just pay close attention which npm you are using 1.x or 2.x with=
 $
> >npm -v
> >
> >--
> >Carlos Santana
> ><csantana23@gmail.com>
>
>

--047d7bd6c6e002c8610503aa0972--