I'm sorry, I don't understand neither see the benefit or value added to
this...
What's the objective of this change?
Are the node_modules platforms going to be usable by separately outside of
Cordova in NodeJS? i.e. Can I use cordova-android to do an android app in
NodeJS using the NPM module?
I'm still trying to understand why we're not using package.json for this. I
seriously do not see any benefit: pls convince me!
On Mon, Jun 2, 2014 at 9:53 PM, purplecabbage purplecabb...@gmail.com
wrote:
$ cordova --usenpm platform add
ios@3.4.1
Why would you do this?
What version of
On Tue, Jun 3, 2014 at 12:53 AM, purplecabbage purplecabb...@gmail.com
wrote:
$ cordova --usenpm platform add
ios@3.4.1
Why would you do this?
Because I want to use version 3.4.1 of cordova-ios.
What version of cordova?
I used cordova-cli @ master
Do you expect to add multiple
Let's stick to the other thread to talk about approach.
On Tue, Jun 3, 2014 at 11:27 AM, Brian LeRoux b...@brian.io wrote:
I'm still trying to understand why we're not using package.json for this. I
seriously do not see any benefit: pls convince me!
On Mon, Jun 2, 2014 at 9:53 PM,
Hi All,
I've added the bits needed to download platform files from npm when doing
cordova platform add
Currently this is hidden behind a --usenpm flag
e.g: cordova --usenpm platform add ios
Some testing would highly appreciated before we switch to npm as the
default place to download the platform
Tried it out. Seemed to work fine:
$ cordova --usenpm platform update ios
npm http GET https://registry.npmjs.org/cordova-ios/3.5.0
npm http 200 https://registry.npmjs.org/cordova-ios/3.5.0
npm http GET https://registry.npmjs.org/cordova-ios/-/cordova-ios-3.5.0.tgz
npm http 200
$ cordova --usenpm platform add
ios@3.4.1
Why would you do this?
What version of cordova?
Do you expect to add multiple ios@versions to a single cordova project?
Ios@3.4.1 and android@3.5.2
Our version / dependency tree is already insane. Has anyone here submitted a
cross device app to a
