Sorry - think I'm mixing up the threads. Totally agree that getting rid of
runtime module loading is the goal here.
cordova_plugins.js now includes a list of installed plugin IDs and their
versions, so we'd want to keep that around and just concat it into
cordova.js with everything else.
modulema
This was the original thing we wanted to get rid of. I understand how we
got here with the refactor towards cordovajs (from seperate cordovajs
implementations in seperate repos) and then plugin extraction.
I see this as just another step on that long refactor to a lightweight,
only-what-we-need, b
browserify does not use them at all, so if we switched to it, there would
be no reason to keep them around. If you see one, please share specifics.
On Tue, Apr 8, 2014 at 11:17 AM, Andrew Grieve wrote:
> I don't see it as an improvement to retire these. Even if we did retire
> them, I don't thi
I don't see it as an improvement to retire these. Even if we did retire
them, I don't think we should do so at the same time as changing to
browserify (the two don't seem related).
On Fri, Apr 4, 2014 at 4:51 PM, Anis KADRI wrote:
> I believe that we can retire these things if we switch to brows
I believe that we can retire these things if we switch to browserify. If
anybody has an objection, please share.
