On Wed, Apr 9, 2014 at 4:55 PM, Jonathan Bond-Caron <[email protected] > wrote:
> On Tue Apr 8 03:50 PM, Andrew Grieve wrote: > > > > The question of whether we *need* them is not a good way to phrase it I > think. > > Rather: > > Pros? > > - Cordova doesn't pick a style of writing modules/plugins > - More control over how plugin loading works > > Prefer this approach for now, might be a better way to do this eventually: > https://plus.google.com/+PaulIrish/posts/cHLhcSfJyJo > > Good points by Alex Young, James Burke > > > Cons? > > - No way to require() or import() other plugins, e.g. extend a plugin > Can you please clarify (with an example)? > - Difficult to "test" cordova plugins > Can you please clarify (with an example)? > - Shouldn't need to compile/transform/transpile a plugin to test it > This is a temporary solution to make existing plugins work without modification. > > > Worth changing at this point? > > Not a fan of any 'bundling' tool with so many dependencies: > https://github.com/substack/node-browserify/blob/master/package.json > https://github.com/webpack/webpack/blob/master/package.json > > This is a fair statement but I'd rather delegate to simplify than reinvent the wheel (and leave it to rust). Those two seem like they could be the right solution for now. If there are (or will be) better bundling tools out there they hopefully (will) support node/commonJS and we won't have to change our current plugins implementation. > The ES6 web modules situation is evolving, but still messy: > https://github.com/addyosmani/es6-tools > > Seems better to experiment more >
