We found out the hard way that having any git-based dependencies causes install to fail if the user doesn't have git installed. For this reason, if something's going to be an npm modules that's depended on, it must be published to npm, and thus go through the proper release process.
Note though that the release process isn't the motivator for this, rather, it's the pain of co-ordinating changes to multiple repositories that depend on each other. On Tue, Apr 15, 2014 at 5:21 PM, Carlos Santana <csantan...@gmail.com> wrote: > On Tue, Apr 15, 2014 at 9:07 PM, Carlos Santana <csantan...@gmail.com>wrote: > >> I agree that braking things into small node modules with clear scope and >> function is good and then be shared across other modules that declare them >> ad dependencies. >> >> These common node modules...: >> 1. don't have to be publish to npm or release as a apache/cordova dist >> asset. >> 2. can live in their own git repos >> 3. can be specified as dependencies using git url, manage during dev with >> npm link or git submodules to do test integration while doing dev >> 4. can be treated as common source code to the cordova tools, and not a >> standalone general purpose tool >> 5. what actually gets publish to npm and release as a apache/cordova dist >> asset continue to be plugman and cordova-cli >> >> --Carlos >> >> > This was just things to consider not necessary a proposal. > But wanted to point out that things can be broken up into modules, and not > necessary add overhead on npm and release process/voting, and just treated > as a SCM exercise.
