cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: cordova cli global vs. local install
Date Tue, 10 Sep 2013 09:55:27 GMT
cd 3.0
npm link .
cd ..
cordova -v

cd 3.1
npm link .
cd ..
cordova -v

Very gruntable


@purplecabbage
risingj.com


On Mon, Sep 9, 2013 at 9:27 PM, Tommy-Carlos Williams <tommy@devgeeks.org>wrote:

> Or, we could just drop it... and just write a blog post on how to use a
> local cordova vs the global one in projects you want to have a specific
> version (i.e.: some script code example wrapper for a cordova command in
> ./node_modules/.bin/cordova).
>
> 0.o
>
> - tommy
>
>
>
> On 10/09/2013, at 1:42 PM, Michal Mocny <mmocny@chromium.org> wrote:
>
> > An alternative to leveraging npm locally may be to split cli/lib node
> > modules as proposed, but just use the existing .cordova/config.json file
> to
> > specify the cordova lib location.  By default, cordova-cli uses the
> global
> > npm install of cordova-lib, but that could be overwritten just like
> > platform versions.  This would also support both a "global lib, upgrade
> all
> > at once" as well as a "local lib, upgrade on demand" workflow.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message