Just as an aside, I have resorted to:

alias cdv="./node_modules/.bin/cordova"

Heh.
On 10/01/2015 8:06 am, "Tommy Williams" <[email protected]> wrote:

> +1 for what Michal describes. Better going forward as well as backwards
> compatibility.
>
> Win win?
> On 10/01/2015 7:54 am, "Michal Mocny" <[email protected]> wrote:
>
>> I like the way gulp works: the same package acts different when installed
>> globally/locally.  Namely, the global always shells work off to the local.
>>
>> So, instead of a separate cordova-local utility (akin to grunt and
>> grunt-cli), perhaps we just add your feature directly into cordova-cli?
>>
>> For backwards compat, I think we should still allow the global cordova-cli
>> to do work as we do now (i.e. we don't *require* local installs), but if a
>> local install happens to exist it would shell out to that.
>>
>> Anyway, neat that you've implemented this already!
>>
>> On Fri, Jan 9, 2015 at 3:41 PM, Staci Cooper <[email protected]> wrote:
>>
>> > A while ago I made a utility called cordova-local for managing multiple
>> > local Cordova installations. It's similar to how grunt/grunt-cli works;
>> > once installed globally, you run 'cordova-local' instead of 'cordova'
>> and
>> > it will locate and pass its arguments off to the closest installation.
>> >
>> > It's kept and installed independently of the cli but my initial idea
>> was to
>> > keep it in the cordova-cli repo. Since that would complicate the
>> > tools-release/versioning process I closed that PR and would like to
>> propose
>> > including it as a new repo. I added some specs and docs and put it in a
>> > utilities repo that could be used for similar cli-independent tools,
>> > currently here: https://github.com/stacic/cordova-utility. I added some
>> > tests to it and also made PRs for documenting the utility in
>> cordova-docs
>> > <https://github.com/apache/cordova-docs/pull/259> and adding it to the
>> > tools release in cordova-coho
>> > <https://github.com/apache/cordova-coho/pull/61>.
>> >
>> > Opinions? Concerns?
>> >
>>
>

Reply via email to