So the question is what would it take to have cordova version not bind to meteor version. Would it be possible to use npm to update cordova like any other npm package ?
I might be wrong but I believe that it is the latest piece that would enable meteor to have a longer release cycle without having much impact.
Any information on that mater, even pointer to what would it take to make it happens (for an eventual PR ) would be much appreciated
I completely agree, it would be really helpful if we could uncouple Cordova from Meteor releases. And I think the extra step of having people install Cordova through npm is worth the gain in transparency and the ability to update independently.
I think the main issue holding that back is that cordova-lib is currently included in the dev bundle and is relied on by CLI code in commands.js and commands-cordova.js. So you probably want to add checks to see whether cordova-lib has been installed and show installation instructions if it hasn’t.
You may also want to have a look at the CordovaProject class and the platform/plugin pinning we currently do.