Or, we could just drop it... and just write a blog post on how to use a local cordova vs the global one in projects you want to have a specific version (i.e.: some script code example wrapper for a cordova command in ./node_modules/.bin/cordova).
0.o - tommy On 10/09/2013, at 1:42 PM, Michal Mocny <mmo...@chromium.org> wrote: > An alternative to leveraging npm locally may be to split cli/lib node > modules as proposed, but just use the existing .cordova/config.json file to > specify the cordova lib location. By default, cordova-cli uses the global > npm install of cordova-lib, but that could be overwritten just like > platform versions. This would also support both a "global lib, upgrade all > at once" as well as a "local lib, upgrade on demand" workflow.
