package.json vs config.xml for cordova plugins

Edit: second update! 2017.05.

It changes again – this time on Cordova side.
Cordova 7 adds support for package.json!

See on Cordova blog: http://cordova.apache.org/news/2017/05/04/cordova-7.html

Edit: update 2016.05.

It seems that many ionic commands were created due to lack of the features in cordova, but since cordova caught up and implemented many new features, the ionic maintainers are considering dumping their command like ionic state in favor of the ones provided by cordova.

So it seems that going the “cordova way” might be more future-proof.

See those tickets:

  • https://github.com/driftyco/ionic-cli/issues/904
  • https://github.com/driftyco/ionic-cli/issues/1324

Original answer (2016.03.):

It’s a matter of person taste I’d say. Whatever solution you go through, it’s best to be consistent and then always use cordova plugin add ... or ionic plugin add and not mix the two.

FYI you can have version pinning with ionic’s solution, but true, you have to put it manually, or you have to specify the version explicitly during installation e.g. ionic plugin add [email protected]. Definitely there’s room for improvements in ionic CLI regarding that.

For example, this is our package.json with pinned plugin versions and platform versions as well, and also pinned github SHA1:

  "cordovaPlugins": [
    "[email protected]",
    "[email protected]",
    "[email protected]",
    {
      "locator": "https://github.com/Initsogar/cordova-webintent.git#3d12378de9f38be900761a0ad06ab697cf6d9add",
      "id": "com.borismus.webintent"
    },
    {
      "variables": {
        "APP_ID": "123456789987654321",
        "APP_NAME": "TEST"
      },
      "locator": "[email protected]",
      "id": "[email protected]"
    }
  ],
  "cordovaPlatforms": [
    "[email protected]"
  ]

Then when you do ionic state restore it will honor the versions listed.

Leave a Comment

techhipbettruvabetnorabahisbahis forumu