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 - Difficult to "test" cordova plugins - Shouldn't need to compile/transform/transpile a plugin to test it > 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 The ES6 web modules situation is evolving, but still messy: https://github.com/addyosmani/es6-tools Seems better to experiment more
