Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
3.3.0
-
None
-
None
Description
There's a major piece of the puzzle missing from the package management capabilities of the CLI, that I haven't seen any discussion/info on yet.
So I'm sorry if this is already planned, but I've searched around and can't see anything.
There doesn't appear to be anything in cordova that saves the list of installed plugins and their installed version.
Ideally I should be able to install a plugin, i.e.
cordova plugin add org.apache.cordova.network-information
And some sort of "plugins.json" file should be created/updated, specifying that the plugin was installed at version 3.0.0.
(like what NPM or bower do with components.json/bower.json)
That file only (and not any of the "artefacts" or vendor code in the `plugins` directory) should be version controlled.
I should then be able to checkout my code from version control into a fresh location and run some sort of command like
cordova plugin install
or something, which would go through the plugins.json file and ensure they have all been installed at the versions specified.
I'm assuming this is on the radar of things to do for the CLI, because it's pretty standard fare for package management functionality.
For me, this is a high sort of priority, because currently using cordova CLI with version control sucks and is a pain when working with multiple developers.
I currently have to version control both the `platforms` and `plugins` directories, despite them being "build artefacts" of the CLI - because there is no current way to check the code out from version control and have the CLI re-build everything correctly.
I'd love to not have to store all that redundant 3rd party code in my repo, and having a `bundle install` like ability would make it so much easier when working with multiple people on a cordova project.
Attachments
Issue Links
- duplicates
-
CB-4624 Allow apps to specify plugin dependencies within their config.xml
-
- Closed
-