Max also hangs out on #phonegap on irc.freenode.net fairly consistently if you wanna chat him up
On 10/2/12 12:34 PM, "Mike Reinstein" <reinstein.m...@gmail.com> wrote: >haha, nice. Yeah, I actually spent a large portion of this week reading >npm's source. isaacs did a really nice job on it. npm's package.json lists >a number of module dependencies that will be very helpful for us as well >me >thinks. > >-Mike > >On Tue, Oct 2, 2012 at 3:28 PM, Andrew Lunny <alu...@gmail.com> wrote: > >> Mike: get in contact with @maxogden - I think he did some work with Fil >>on >> this stuff, and he knows NPM inside out. Unfortunately, he's too cool >>for >> Apache mailing lists. >> >> On 2 October 2012 12:10, Mike Reinstein <reinstein.m...@gmail.com> >>wrote: >> >> > Okay cool, sounds reasonable. I will try to hhack something up this >> week; I >> > have a few ideas in mind for this. :) >> > >> > onward! >> > >> > -Mike >> > >> > On Tue, Oct 2, 2012 at 2:53 PM, Brian LeRoux <b...@brian.io> wrote: >> > >> > > > Maybe I'm wrong but after reading >>https://npmjs.org/doc/json.htmlI'm >> > > > under the impression this is solely for specifying the required >> > > version(s) >> > > > of node to use the npm package. >> > > >> > > correct. we'd extend it with support for something like. >> > > >> > > { "engines" : { "cordova" : ">=2.2.0" } } >> > > >> > > >> > > >> > > > The problem is before allowing someone to register a plugin... >> > > >> > > ya. npm registry is unique by pkg name; no collision fear. other >> > > checks can be added or maybe built w/ that tool you're talking about >> > > for sure. >> > > >> > >>
