cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Mocny (JIRA)" <>
Subject [jira] [Commented] (CB-8153) Cordova Browserify based prepare should still create a plugin metadata file.
Date Mon, 15 Dec 2014 03:06:14 GMT


Michal Mocny commented on CB-8153:

I don't like package.json for a few reasons:

1. package.json makes sense at the root of a cordova project, but suggesting we add generate
one for each platform makes less sense to me.  Would it include the app preprocessing tools
the developer used?  If it would only have the platform version, plugin versions, and (maybe)
tooling versions used, then why is a full package.json needed?  Other than dependencies, what
other fields would we use?  If it could replace all of config.xml then maybe it would make
sense, but I don't think it can.

2. package.json dependencies refer to npm packages (or explicit git repos), not plugin ids
using our plugin dependency format.

3. I would not like to block this minor feature request (actually, I'm just asking that we
don't have a feature regression) on the fairly major change of adding a package.json to cordova

Again, I think package.json is a good idea, but we should discuss in context of cordova-cli
4.0 and how to do it right.

I think adding this info to config.xml would be fine, but would prefer a single cordova_plugins.js/json

> Cordova Browserify based prepare should still create a plugin metadata file.
> ----------------------------------------------------------------------------
>                 Key: CB-8153
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CordovaLib
>            Reporter: Michal Mocny
>            Priority: Minor
> If we move away from cordova_plugins.js and onto browserify concat for plugin js modules,
it would still be useful to retain some plugin metadata file.
> Hopefully it can be as simple as a json file with { pluginId: pluginVersion } or something
like that.
> Being able to quickly figure out which plugins a given app was built with has come up
as useful in the past, even if only for informational purposes!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message