Let's stick to the other thread to talk about approach.
On Tue, Jun 3, 2014 at 11:27 AM, Brian LeRoux <[email protected]> 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, purplecabbage <[email protected]> > wrote: > > > >> $ cordova --usenpm platform add > > >> [email protected] > > > > Why would you do this? > > What version of cordova? > > Do you expect to add multiple ios@versions to a single cordova project? > > [email protected] and [email protected] > > > > Our version / dependency tree is already insane. Has anyone here > submitted > > a cross device app to a store? Made anything more complicated than hello > > world? I feel like we're losing touch. > > > > Sent from my iPhone > > > > > On Jun 2, 2014, at 7:49 PM, Andrew Grieve <[email protected]> > wrote: > > > > > > 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 > > https://registry.npmjs.org/cordova-ios/-/cordova-ios-3.5.0.tgz > > > iOS project is now at version 3.5.0 > > > > > > $ ls ~/.cordova/lib/npm_cache/cordova-ios/3.5.0/ > > > .cache.json package/ package.tgz > > > > > > $ cordova --usenpm platform update ios > > > npm http GET https://registry.npmjs.org/cordova-ios/3.5.0 > > > npm http 304 https://registry.npmjs.org/cordova-ios/3.5.0 > > > iOS project is now at version 3.5.0 > > > > > > $ cordova --usenpm platform update [email protected] > > > Platform "[email protected]" not recognized as a core cordova platform. See > > > `cordova platform list`. > > > > > > $ cordova --usenpm platform add [email protected] > > > Platform "[email protected]" not recognized as a core cordova platform. See > > > `cordova platform list`. > > > > > > > > > Thoughts for next steps: > > > - Allow platform@version in the command-line (as I tried to do) > > > - Delete "url" and "version" from platforms.js (WOOHOO!) > > > - Add "cordova cache ls" and "cordova cache clear" commands > > > - Advertise the new awsomeness! > > > > > > > > > > > > > > >> On Mon, Jun 2, 2014 at 5:46 PM, Brian LeRoux <[email protected]> wrote: > > >> > > >> but…why not package.json ? > > > (leaving this discussion to the other thread) > > > > > >> > > >> > > >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky <[email protected]> > > wrote: > > >>> > > >>> 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 files from. > > >>> > > >>> > > >>> The links changes in cordova-lib > > >>> < > > >> > > > https://github.com/apache/cordova-lib/commit/55810360fe660276a1ab0d04382da633f9cf1290 > > >>> and > > >>> cordova-cli > > >>> < > > >> > > > https://github.com/apache/cordova-cli/commit/57179d61d0c35e32c808198d184d0d515fbb0c28 > > >>> > > >>> Some of the platforms on npm: > > >>> https://www.npmjs.org/package/cordova-android > > >>> https://www.npmjs.org/package/cordova-ios > > >>> https://www.npmjs.org/package/cordova-blackberry > > >> > > >
