Re: MobileSpec for testing cordova-lib@rc

Why rename plugins now? I think the plugin.xml can remain the same even with the move to npm. Its just the npm package name that would be new. I think we have enough ongoing ideas (see also Gorkems work), that we should put together a doc / have a hangout before making any significant changes.

Re: MobileSpec for testing cordova-lib@rc

In terms of discoverability, It seems like npm is going to make ecosystem/collection searches a first class thing [1] [2] "An early discussion of collections is taking place on GitHub issues, and npm ecosystems are starting to

Re: MobileSpec for testing cordova-lib@rc

Having two different names for the same plugin would be pretty annoying (if it's not something trivial like nameB = prefix + nameA). If reverse-domain-style IDs are not really necessary, I would be glad to see them eventually replaced with shorter and more memorable names. For CLI based projects,

Re: MobileSpec for testing cordova-lib@rc

So, `npm install` will look at the project root package.json and install all "dependencies" in the npm package format. `cordova plugin add` will take the plugin_ID and look in your plugin_search_path's for plugins with that ID, and fallback to fetching from our plugin registry if it does not find

Re: MobileSpec for testing cordova-lib@rc

On Thu, Jan 8, 2015 at 8:39 PM, Steven Gill wrote: > Just checked out peer-dependencies. Looks like the way to move forward with > handling our dependency issues. > > Right now, plugman publish creates a package.json file by grabbing info > from plugin.xml. Once published, plugman will automatica

Re: MobileSpec for testing cordova-lib@rc

Just checked out peer-dependencies. Looks like the way to move forward with handling our dependency issues. Right now, plugman publish creates a package.json file by grabbing info from plugin.xml. Once published, plugman will automatically delete the package.json file. I suggest we stop deleting t

Re: MobileSpec for testing cordova-lib@rc

+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 de

Re: MobileSpec for testing cordova-lib@rc

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 wrote: > On Thu, Jan 8,

Re: MobileSpec for testing cordova-lib@rc

On Thu, Jan 8, 2015 at 3:47 PM, Michal Mocny 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 = [

Re: MobileSpec for testing cordova-lib@rc

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? 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

Re: MobileSpec for testing cordova-lib@rc

Nice! Great example of how to use the JS API. On Thu, Jan 8, 2015 at 2:55 PM, Mark Koudritsky wrote: > Josh, thanks for the suggestion. Added it here > < > https://github.com/kamrik/cordova-test-rc/commit/d3a1abeda45357c4cf32b28e6e63cc269d7d3bda > > > as > process.env.HOME = path.join(__dirname,

Re: MobileSpec for testing cordova-lib@rc

Josh, thanks for the suggestion. Added it here as process.env.HOME = path.join(__dirname, 'home'); On Thu, Jan 8, 2015 at 2:19 PM, Josh Soref wrote: > Mark Koudritsky wrote: > >Trying to run MobileSpec w

Re: MobileSpec for testing cordova-lib@rc

Mark Koudritsky wrote: >Trying to run MobileSpec with the tools release candidate yesterday >inspired me to write a script that would do it all with a single command >and a local installation of cordova-lib@rc without affecting the global >install/link. This also turned out to be a good example of

MobileSpec for testing cordova-lib@rc

Trying to run MobileSpec with the tools release candidate yesterday inspired me to write a script that would do it all with a single command and a local installation of cordova-lib@rc without affecting the global install/link. This also turned out to be a good example of how to use cordova via JS