Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of kamrik@google.com designates
 209.85.192.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMSbhBi0BqKAA3M5nCCwzFfDjWW_6sF-1oSCyxRojqwcbgrAhw@mail.gmail.com>
References: 
 <CA+GVa3aiGaX4bSaUn29mmHjofcQQ=q3c42F7BBsTXwGYs8JX4g@mail.gmail.com>
 <D0D44208.6F16C%jsoref@blackberry.com>
 <CA+GVa3bjdUeQotAfP4ZUe_0w40ueXmKht52dCUkyeep6udR6zA@mail.gmail.com>
 <CABiQX1Ui3GBS1X7-jS7PckO_fG0Ok55QfpQ+e5eCDvwGLObTDA@mail.gmail.com>
 <CAEeF2TdwDhBBkhasY-EwbrY_+J+28Nyb7_BZfqGzvEjLY9+qgw@mail.gmail.com>
 <CA+GVa3aprKFx_QE061suubJFnB4u4TrctAMQEh9MdJe01JpNfA@mail.gmail.com>
 <CAMSbhBi0BqKAA3M5nCCwzFfDjWW_6sF-1oSCyxRojqwcbgrAhw@mail.gmail.com>
From: Mark Koudritsky <kamrik@google.com>
Date: Thu, 8 Jan 2015 18:36:44 -0500
Message-ID: 
 <CA+GVa3bLP1SGWwCZTr-E8YZHD=wS2_FuMZFSDzXw5ZmtqwHZZA@mail.gmail.com>
Subject: Re: MobileSpec for testing cordova-lib@rc
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=001a1133071e8081ac050c2c84b1

--001a1133071e8081ac050c2c84b1
Content-Type: text/plain; charset=UTF-8

+1 for publishing plugins to npm

We will need to come up with a good naming convention so that translating
from plugin id to npm package name would be trivial. Preferably with some
stable prefix (like cordova_plugin_) so that it would be easy to
distinguish plugins if they are listed with other dependencies in
package.json

Another problem to solve are the dependencies _between_ plugins. We don't
want nested dirs like node_modules/pluginX/node_modules/pluginY or multiple
version of the same plugin (like it happens for regular npm deps). Maybe
npm peer dependencies could be used to solve this
http://blog.nodejs.org/2013/02/07/peer-dependencies/

For experimenting with this, there is no need to modify cordova-lib. We
just need to publish some experimental plugins to npm registry, let npm
download them during npm install and then add ./node_modules to searchpath.
I tried this with platforms in https://github.com/kamrik/CordovaGulpTemplate


On Thu, Jan 8, 2015 at 6:02 PM, Steven Gill <stevengill97@gmail.com> wrote:

> This is rad! Definitely a great example showing the JS API.
>
> I am thinking about also starting to publish our plugins to npm and add a
> flag to plugman install to fetch from npm instead of cordova plugins
> registry. Thoughts?
>
> On Thu, Jan 8, 2015 at 1:09 PM, Mark Koudritsky <kamrik@google.com> wrote:
>
> > On Thu, Jan 8, 2015 at 3:47 PM, Michal Mocny <mmocny@chromium.org>
> wrote:
> >
> > > If we add node_modules to search path, will we be able to adjust which
> > > versions of platforms/plugins it uses just by modifying package.json?
> > >
> > >
> > Since platforms can be added by path. You can replace
> > platforms = ['android']
> > with
> > platforms = ['/path/to/local/cordova-android']   // Should work for using
> > e.g. cordova-android 4.x
> > or
> > platforms = ['../node_modules/cordova-android']
> >
> >
> > > Not sure if platforms use search path, or just plugins?  Also not sure
> if
> > > we can install plugins from our registry using npm proper, but you can
> > use
> > > the git repos as a workaround if not.
> > >
> >
> > For plugins it's more tricky (other npm repo, different dependency
> model).
> > Some options are:
> >  - use private cordova subsection in package.json and store plugin info
> > including versions there in whatever format  we want
> >
>

--001a1133071e8081ac050c2c84b1--