+1 for the more straight forward easy win of the grunt/grunt-cli model. I see the benefits of Michal's suggestion, but I agree that our efforts are best spent elsewhere.
Let users take control of versions as with other npm modules/frameworks/libs. Just set the cordova version in package.json. With core no longer having all the apis in it, it's no longer a massive dep, so having it downloaded for each project is less of an issue, surely? - tommy On 10/09/2013, at 1:48 AM, Carlos Santana <[email protected]> wrote: > What does the community think of installing cordova only locally and not > globally? > > # Installing Cordova locally will provide: > > - A way to use different versions of cordova on the same system/os. > - A way to specify cordova as a dependency in package.json for an App > project > - A way to sandbox cordova and checking into source control for an App > project > > # [GruntJS](http://gruntjs.com/getting-started) is a project that already > takes this approach: > > 1. User installs `grunt-cli` globally instead of grunt > npm -g install grunt-cli` > > 2. User installs `grunt` locally > npm install grunt --save-dev > > 3. When user runs `grunt` it will run a short script `/usr/local/bin/grunt` > (about 40 lines) > It will resolve and use grunt from cwd (current working directory) > locally > > # Proposal: > > 1. Have 2 npm packages > - cordova-cli > - cordova > > 2. create cordova-cli package and update docs > cordova-cli will be almost indentical to grunt-cli > https://github.com/gruntjs/grunt-cli/blob/master/bin/grunt > > 3. codova package is not longer get's install as `bin\cordova` and instead > run with > require(cordovapath).cli(); > > > --- > If you want to know more about grunt and why grunt swtiched from being > installed globally to now being install locally a podcast came out last > Friday where the author of GruntJS (Ben Alman) explains more details > http://javascriptjabber.com/074-jsj-grunt-js-with-ben-alman/ > > > -- > Carlos Santana > <[email protected]>
