In general, I'm not opposed to the mindset that you get a "proven working" combination of modules with whatever version of Cordova you're using and then updating those modules as desired.
I imagine this is similar to downloading an installer for a desktop application, which then installs an update right after the initial installation. >From your initial assessment, I would conclude that the actual issue is that >the user will not realize that newer packages may be available. I would >suggest leaving the version pinning in place and instead add update checks as >applicable. Maybe along the lines of https://github.com/yeoman/update-notifier If that's not acceptable, I would prefer dropping version pinning and putting emphasis on the latest versions of the modules. The old versions of platforms and other modules are losing importance constantly, because technologies are deprecated and removed all the time. I don't even know what I could do today with a 2 year old Cordova version; pinned versions or not. So providing users with the best code possible (which should be the latest) should be preferred. [ Full content available at: https://github.com/apache/cordova/issues/18 ] This message was relayed via gitbox.apache.org for [email protected]
