+1 for platforms on npm. -1 for plugins on npm (best way to create a giant mess).
On Mon, Mar 31, 2014 at 4:18 PM, Jonathan Bond-Caron < [email protected]> wrote: > On Sat Mar 29 03:11 PM, Brian LeRoux wrote: > > I think its a great idea. The platforms have a standard interface [1] > for which the > > higher level CLI Node module depends. We could remove our logic for > > versioning/caching and leave that to npm. We distribute via npm already > for the > > CLI so this is just a natural extension. We'd win less code, and a > cleaner > > implementing focused on the CLI needs not dependency management (that npm > > does better). > > > > Sounds good to me, platforms make sense on npm, expected to run in node.js > environment > > > Hosting our Plugins on the vanilla npm registry won't work. We > investigated that > > path. (Though I welcome anyone here to do their own research.) > Ultimately, we > > have a different set of needs on installation, and and in the act of > packaging. > > We'd win distribution, but we have that already, so we'd be solving > nothing. > > > > Agree with all of Andrew's points, recently looked into 'bower': > > http://tech.pro/tutorial/1190/package-managers-an-introductory-guide-for-the-uninitiated-front-end-developer#front_end_developers > > Dependencies are flat which resembles a bit more cordova: > > - npm things (~ node.js javascript / v8 runtime) > - cordova things (native code + javascript, multiple webviews) > - bower things (javascript, multiple browsers) > > Bower things are compatible with cordova, might be worth looking into. > >
