Re: npm based "cordova platform add"

2014-06-09 Thread Victor Sosa 
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?
What are the benefits of npm approach instead of the current library in
$HOME/.cordova approach?
Is there gonna be a breakage in the Cordova API? Many developer already
complain about the huge changes introduced in service versions.

Better to have a talk about this in tomorrow's hangout.


2014-06-03 11:03 GMT-05:00 Brian LeRoux :

> package.json does all of this
>
>
> On Tue, Jun 3, 2014 at 8:55 AM, Andrew Grieve 
> wrote:
>
> > On Tue, Jun 3, 2014 at 12:53 AM, purplecabbage 
> > 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 ios@versions to a single cordova
> project?
> > >
> > No. Just want to be able to tell it what version of cordova-ios to use
> when
> > adding or updating the platform.
> >
> >
> > > Ios@3.4.1 and android@3.5.2
> > >
> > Exactly. In order for platforms to ship separately, they must be
> versioned
> > separately.
> >
> >
> > >
> > > 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.
> > >
> > Worrisome that you feel this way, but this is not actionable feedback.
> >
> >
> >
> > >
> > > Sent from my iPhone
> > >
> > > > On Jun 2, 2014, at 7:49 PM, Andrew Grieve 
> > 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 ios@3.4.1
> > > > Platform "ios@3.4.1" not recognized as a core cordova platform. See
> > > > `cordova platform list`.
> > > >
> > > > $ cordova --usenpm platform add ios@3.4.1
> > > > Platform "ios@3.4.1" 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  wrote:
> > > >>
> > > >> but…why not package.json ?
> > > > (leaving this discussion to the other thread)
> > > >
> > > >>
> > > >>
> > > >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky  >
> > > 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
> > > >>
> > >
> >
>



-- 
Victor Adrian Sosa Herrera
IBM Software Engineer
Guadalajara, Jalisco

Re: npm based "cordova platform add"

2014-06-03 Thread Brian LeRoux 
package.json does all of this


On Tue, Jun 3, 2014 at 8:55 AM, Andrew Grieve  wrote:

> On Tue, Jun 3, 2014 at 12:53 AM, purplecabbage 
> 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 ios@versions to a single cordova project?
> >
> No. Just want to be able to tell it what version of cordova-ios to use when
> adding or updating the platform.
>
>
> > Ios@3.4.1 and android@3.5.2
> >
> Exactly. In order for platforms to ship separately, they must be versioned
> separately.
>
>
> >
> > 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.
> >
> Worrisome that you feel this way, but this is not actionable feedback.
>
>
>
> >
> > Sent from my iPhone
> >
> > > On Jun 2, 2014, at 7:49 PM, Andrew Grieve 
> 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 ios@3.4.1
> > > Platform "ios@3.4.1" not recognized as a core cordova platform. See
> > > `cordova platform list`.
> > >
> > > $ cordova --usenpm platform add ios@3.4.1
> > > Platform "ios@3.4.1" 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  wrote:
> > >>
> > >> but…why not package.json ?
> > > (leaving this discussion to the other thread)
> > >
> > >>
> > >>
> > >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky 
> > 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
> > >>
> >
>

Re: npm based "cordova platform add"

2014-06-03 Thread Andrew Grieve 
Let's stick to the other thread to talk about approach.


On Tue, Jun 3, 2014 at 11:27 AM, Brian LeRoux  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 
> wrote:
>
> > >> $ 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 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 
> 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 ios@3.4.1
> > > Platform "ios@3.4.1" not recognized as a core cordova platform. See
> > > `cordova platform list`.
> > >
> > > $ cordova --usenpm platform add ios@3.4.1
> > > Platform "ios@3.4.1" 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  wrote:
> > >>
> > >> but…why not package.json ?
> > > (leaving this discussion to the other thread)
> > >
> > >>
> > >>
> > >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky 
> > 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
> > >>
> >
>

Re: npm based "cordova platform add"

2014-06-03 Thread Andrew Grieve 
On Tue, Jun 3, 2014 at 12:53 AM, purplecabbage 
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 ios@versions to a single cordova project?
>
No. Just want to be able to tell it what version of cordova-ios to use when
adding or updating the platform.


> Ios@3.4.1 and android@3.5.2
>
Exactly. In order for platforms to ship separately, they must be versioned
separately.


>
> 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.
>
Worrisome that you feel this way, but this is not actionable feedback.



>
> Sent from my iPhone
>
> > On Jun 2, 2014, at 7:49 PM, Andrew Grieve  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 ios@3.4.1
> > Platform "ios@3.4.1" not recognized as a core cordova platform. See
> > `cordova platform list`.
> >
> > $ cordova --usenpm platform add ios@3.4.1
> > Platform "ios@3.4.1" 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  wrote:
> >>
> >> but…why not package.json ?
> > (leaving this discussion to the other thread)
> >
> >>
> >>
> >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky 
> 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
> >>
>

Re: npm based "cordova platform add"

2014-06-03 Thread Brian LeRoux 
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 
wrote:

> >> $ 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 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  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 ios@3.4.1
> > Platform "ios@3.4.1" not recognized as a core cordova platform. See
> > `cordova platform list`.
> >
> > $ cordova --usenpm platform add ios@3.4.1
> > Platform "ios@3.4.1" 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  wrote:
> >>
> >> but…why not package.json ?
> > (leaving this discussion to the other thread)
> >
> >>
> >>
> >>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky 
> 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
> >>
>

Re: npm based "cordova platform add"

2014-06-02 Thread purplecabbage 
>> $ 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 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  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 ios@3.4.1
> Platform "ios@3.4.1" not recognized as a core cordova platform. See
> `cordova platform list`.
> 
> $ cordova --usenpm platform add ios@3.4.1
> Platform "ios@3.4.1" 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  wrote:
>> 
>> but…why not package.json ?
> (leaving this discussion to the other thread)
> 
>> 
>> 
>>> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky  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
>>

Re: npm based "cordova platform add"

2014-06-02 Thread Andrew Grieve 
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 ios@3.4.1
Platform "ios@3.4.1" not recognized as a core cordova platform. See
`cordova platform list`.

$ cordova --usenpm platform add ios@3.4.1
Platform "ios@3.4.1" 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  wrote:

> but…why not package.json ?
>
(leaving this discussion to the other thread)

>
>
> On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky  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
> >
>

Re: npm based "cordova platform add"

2014-06-02 Thread Brian LeRoux 
but…why not package.json ?


On Mon, Jun 2, 2014 at 3:28 PM, Mark Koudritsky  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
>

npm based "cordova platform add"

2014-06-02 Thread Mark Koudritsky 
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

and
cordova-cli


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