The real question is do we vote on it before posting to npm. Since it isn't for general release distribution, but just for testing, I would say you don't have to vote on it.
Thoughts? -Steve On Fri, Mar 4, 2016 at 10:43 AM, Richard Knoll <[email protected]> wrote: > Yep, I would like to test with a plugin on npm to support the new version > selection feature I'm about to merge. > > Thanks, > Richard > > -----Original Message----- > From: Steven Gill [mailto:[email protected]] > Sent: Friday, March 4, 2016 10:41 AM > To: [email protected] > Subject: Re: Test Plugin on npm > > Hey Byoungro, > > We already test local plugins. I think the point of Richard asking is so > we actually test our npm fetching and installing. > > Cheers, > -Steve > > On Fri, Mar 4, 2016 at 10:37 AM, So, Byoungro <[email protected]> > wrote: > > > Hi Richard, > > > > Do you know you can add the plugin from your local disk path? > > “cordova plugin add <path>” might be easier for you than publishing > > your test plugin on the NPM registry and test using NPM. > > > > Byoungro So > > SSG / DPD / Mobile Computing and Compilers Intel Corporation > > > > From: Richard Knoll > > <[email protected]<mailto:[email protected]>> > > Reply-To: "[email protected]<mailto:[email protected]>" < > > [email protected]<mailto:[email protected]>> > > Date: Friday, March 4, 2016 at 10:30 AM > > To: "[email protected]<mailto:[email protected]>" < > > [email protected]<mailto:[email protected]>> > > Subject: Test Plugin on npm > > > > Hey all, > > > > I'd like to have some better end-to-end tests for "cordova plugin add" > > in cordova-lib, so I wanted to publish a test plugin to npm. The > > plugin itself will be empty besides a plugin.xml, I just need it to > > exist and have engine information I can test against. Do we have an > > official npm account that I should be using for the publishing? I can > > store the plugin itself in cordova-plugins. > > > > Thanks, > > Richard > > > > >
