Thanks Carlos, it's a definite possibility, but due to all the npm troubles, I wiped my npm cache.
On Tue, Mar 4, 2014 at 2:13 PM, Carlos Santana <[email protected]> wrote: > yes blame npm take the easy route out :-) > > One thing it could be is that npm failed to fetch latest from npm registry > (possible related to their ssl certificate issue [1]) and installed from > your npm cache. > > One tip to troubleshoot installations problems with npm, is to clean your > cache > npm cache clean cordova > or > rm -rf ~/.npm/cordova > > > > [1]: > > http://blog.npmjs.org/post/78165272245/more-help-with-self-signed-cert-in-chain-and-npm > > > On Tue, Mar 4, 2014 at 2:08 PM, Michal Mocny <[email protected]> wrote: > > > ..last week I saw 0.1.1 published under the rc, even hours after Andrew > > claimed to release 0.1.2. I figured it was me/him who made a mistake, > but > > given everything, and that npm have been blogging about all sorts of > > quirks.. yes, blame canad^H^H^H^H^H npm. > > > > -Michal > > > > > > On Tue, Mar 4, 2014 at 2:00 PM, Lorin Beer <[email protected]> > > wrote: > > > > > I'm blaming npm for this. > > > > > > With 1.4.4, I am now getting 0.1.2, the rc, instead of 0.1.0. > > > > > > Evidently not our issue, so ignore my "unpublish" suggestion. > > > > > > > > > On Mon, Mar 3, 2014 at 4:48 PM, Carlos Santana <[email protected]> > > > wrote: > > > > > > > I just tried with npm 1.4.3 (version included with v0.10.26) > > > > I got: > > > > > > > > $ npm install -g cordova > > > > > > > > $ npm ls -g cordova > > > > > > > > /Users/csantana23/.nvm/v0.10.26/lib > > > > > > > > └── [email protected] > > > > > > > > When I do "npm view cordova" I see this > > > > > > > > { name: 'cordova', > > > > > > > > description: 'Cordova command line interface tool', > > > > > > > > 'dist-tags': { latest: '3.4.0-0.1.0', rc: '3.4.0-0.1.2' }, > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 3, 2014 at 6:11 PM, Lorin Beer <[email protected] > > > > > > wrote: > > > > > > > > > Weird, that still isn't the latest version. > > > > > > > > > > what version of npm did you use? I'm running 1.4.4 > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 3, 2014 at 3:08 PM, Steven Gill < > [email protected]> > > > > > wrote: > > > > > > > > > > > hmm, I just did a npm install cordova and got 3.4.0-0.1.0 > > > > > > > > > > > > > > > > > > On Mon, Mar 3, 2014 at 2:56 PM, Lorin Beer < > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > Currently, the 3.4.0-rc.2 release currently resolves as > 'higher' > > > than > > > > > the > > > > > > > actual 3.4.0 releases: '3.4.0-0.1.0', '3.4.0-0.1.1', and > > > > '3.4.0-0.1.2', > > > > > > > > > > > > > > you can check this with: > > > > > > > > > > > > > > $ npm view cordova versions > > > > > > > > > > > > > > This means that $ npm install cordova installs rc2 instead of > the > > > > > latest > > > > > > > 3.4.0 release. > > > > > > > > > > > > > > I suggest unpublishing the current rc2 tag and renaming it. > > > > > > > > > > > > > > - Lorin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Carlos Santana > > > > <[email protected]> > > > > > > > > > > > > > -- > Carlos Santana > <[email protected]> >
