We should always update shrinkwrap.json before going thru test, that way if
there is a dependency down the chain (i.e. ALL the chain) that got updated
we can pick up the new version and everybody test the same bits.




On Mon, Sep 15, 2014 at 11:16 PM, Marcel Kinard <[email protected]> wrote:

>
> On Sep 15, 2014, at 10:59 PM, Carlos Santana <[email protected]> wrote:
>
> > Marcel apache git [1] neither github git [2] for cordova-cli repo has
> > cordova-lib pointing to 0.21.11
> > Both have in package.json "cordova-lib"
> > : "0.21.10",
>
> I created a branch for the tools, to avoid picking up new content other
> than the necessary adjustments. Look for the tag.
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=shortlog;h=refs/heads/rb_3.6.0-0.2.8
>
> > Finally the reason that when doing "npm install -g [email protected]"
> is
> > not installing [email protected] and is installing the old version
> 9.2.10
> > is because of npm-shrinkwrap.json inside cordova-cli
>
> Ah crap, it's the npm-shrinkwrap.json file. Now I see it. I didn't update
> the shrinkwrap file because none of the unspecified dependencies were
> updated. But in further reading of the shrinkwrap docs, I now see that the
> shrinkwrap trumps package.json, not the other way around.
>
> (Sound of head banging slowly on the wall repeatedly.)




-- 
Carlos Santana
<[email protected]>

Reply via email to