In Update 5, we will show this info bar whenever you are targeting a Cordova version that is not on the latest version number.For example, if you are targeting 4.x and the latest is 5.x, then you will see this warning when you go to add a plugin.We’ve heard some feedback that this can create a confusing environment for some people.It means any changes made in the CLI are not automatically reflected in Visual Studio, for example.Unfortunately, this can be a big problem for customers who are targeting an older version of Cordova.In cases where there are major platform changes between the version they’re targeting and the edge version, the plugins may not be compatible with the platforms their Cordova version is targeting. The good news is that starting in Cordova 6.0.x, plugins will now be pinned to the platform that is pinned to that CLI.If you already have the tools installed then you can upgrade by clicking this link: Cordova You can download the update now or wait a few weeks for the upgrade notification in Visual Studio.
Until then, we’ve been working on making sure our tooling works with NPM 3.
This means adding a plugin in Cordova 6 will no longer pull the edge version - it will pull a specific version that the Cordova community deemed compatible with 6.0.
Still, there are cases where developerss could be targeting a platform for which we do not have pinning data.
We are discussing ways to make this experience smoother, but to start with we decided to alert developers when their configuration may not support the edge plugin version by adding an info bar to the config designer: We think the steps to resolve this problem are fairly mechanical, but we think the first step is to bring the potential problem to your attention.
We would definitely appreciate feedback on the help link - we want this to be as easy to understand as possible.