npm link is the life saver when working with multiple node modules that you own and have dependencies between them.
On Wed, Apr 16, 2014 at 10:45 AM, Mark Koudritsky <kam...@google.com> wrote: > On Wed, Apr 16, 2014 at 9:59 AM, Carlos Santana <csantan...@gmail.com > >wrote: > > > If you the decision factor is to consolidate all the cli tooling into a > > single git repo, that's ok but > > > > I still think we should treat what's inside the single repo as different > > small independent npm modules and use the bundleDependencies in the cli > and > > plugman pacakge.json > > > > /cordova-the-one-repo-to-rule-them-all > > |- cli > > | '- package.json > > |- plugman > > | '- package.json > > |- common > > | '-util_a/package.json > > | '-util_b/package.json > > | '-util_c/package.json > > > > cli and plugman pacakge.json will contain > > "bundleDependencies": [ > > "util_a", > > "util_b" > > ] > > > > during dev and plublish, coho can automate > > cd cli > > #link dependencies > > npm link ../common/util_a > > npm link ../common/util_b > > > The bundleDependencies method seems good, didn't know about it. > > What happens if util_c also depends on util_a? > I think in that case you I'll need to cd to util_c and also do some linking > magic there. I guess we'll need a script (or several) for setting up the > dev environment. > -- Carlos Santana <csantan...@gmail.com>
