[jira] [Commented] (CB-8153) Cordova Browserify based prepare should still create a plugin metadata file.

["Steve Gill (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CB-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264005#comment-14264005 ] 

Steve Gill commented on CB-8153:
--------------------------------

I'll look into getting the browserify code to generate cordova_plugins.js for backwards compatibility. I'd still like to revisit package.json at a later date, but agree to move the process forward now in hopes of getting this ready to become default.



> Cordova Browserify based prepare should still create a plugin metadata file.
> ----------------------------------------------------------------------------
>
>                 Key: CB-8153
>                 URL: https://issues.apache.org/jira/browse/CB-8153
>             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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org