> > And I would also like to remove the "protective" engine all plugins have > that points the next major version to cordova >= 100 > > +1. I never really understood the rationale behind this. I think it's > safe to assume that a next plugin major will continue to support the > cordova cli that it used to support. If it does not, then we can update > the engines accordingly. >
The idea was, if a breaking change was introduced that required updating engines, but we forgot to update the engines, it would prevent the plugin to install and break user's projects. But in most cases it ended in cases where breaking changes were introduced, but they didn't need updating engines and the "protective" entry ended blocking the plugin install for no reason, so instead of saving us from trouble, it caused trouble. > > So, what I'm proposing is to add engines to all the plugins to require > at > least > cordova 9 > cordova ios 5.1.0 > cordova-android 8.0.0 > > I think an argument could be made that adding these could be breaking in > itself and thus warrant a major release, but at the same time, in > addition to what Julio said, anything pre cordova-android@8 will not be > accepted by Google Play store due to target API requirements, and the > same for pre cordova-ios@5.10 because of the wkwebview requirement. So I > still give a +1 on this. > It's not really a breaking change if we replace the existing protective entry with these new requirements, since the new requirements are only for the next major release, and won't have any effect until we release a major version.
