cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian LeRoux...@brian.io>
Subject Re: adding platforms to npm for dependency sanity
Date Wed, 04 Jun 2014 18:17:57 GMT
Using package.json and npm for dependencies is what those things are
designed for. Those are the conventions of the platform we use: Node. This
IS simpler, following the principle of least surprise: an expected by our
developer audience.

On Jun 4, 2014 8:55 AM, "Marcel Kinard" <cmarcelk@gmail.com> wrote:

> What Tommy describes here makes some sense.
>
> But what I’m still struggling to see is how the kind of changes in this
> thread are a win for Cordova users, in terms such as simplified workflow, a
> more predictable consistent tested combination of tools/platforms/plugins,
> and especially performing an upgrade. It feels like the proposals here are
> making those user terms a bit more complicated.
>
> On Jun 3, 2014, at 7:38 PM, tommy-carlos williams <tommy@devgeeks.org>
> wrote:
>
> > If the cordova cli was globally installed, but basically a thin wrapper
> like grunt-cli…
> >
> > create:
> >
> > cordova create foo
> > cd foo
> > npm install —save cordova@x.y.z
> > cordova platform add android
> > cordova platform add ios
> >
> > cordova create bar
> > cd bar
> > npm install —save cordova@x.y.n
> > cordova platform add ios
> > cordova platform add android
> >
> > update:
> >
> > cd bar
> > npm install —save cordova@x.y.z
> > cordova update ios
> > cordova update android
>
>

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