Closed josundt closed 2 years ago
Thx for the interesting finding! This could affect some other plugins if they extend core classes.
Tested v1.5.0, works with or without dist rewrite now.
I skipped two dist folders (amd, system) because nobody needs to use them.
Tested upgrading and now everything works like charm! Thanks for the extremely low response time! 🙂 I find it heart warming whenever I witness open source projects where maintenance is taken seriously!
I have an app using aurelia 1.0 with webpack/aurelia-webpack-plugin.
The
aurelia-webpack-plugin
has adist
setting that lets you decide which distribution/transpiled ES target from the aurelia packages/plugins to pick when bundling.Aurelia uses the following convention for subfolder layout in their own packages and also recommend this for plugin creators::
native-modules
: esm/es5es2015
: esm/es2015es2017
: esm/es2017es20**
: esm/es20**The aurelia-webpack-plugin
dist
setting lets you choose which target to include when bundling. This works foraurelia-*
packages and should also work for aurelia plugins that follow the package folder layout convention.I recently tried to change the
aurelia-webpack-plugin
setting fromnative-modules
toes2017
, but then thereorderable-repeat
plugin failed. Everything else actually works like charm.I found that the reason is that the reorderable-repeat plugin is only transpiled to es5, and the code also expects the aurelia
AbstractRepeater
to be using the prototype pattern (not es2015+ class) when theReorderableRepeat
attempts to extend it. This would not have been a problem if theReorderableRepeat
was transpiled to es2015+ with Babel.Transpiled code from reorderable-repeat.js:
Proposed solution:
I would really appreciate if you could look into this. It should not be a to big effort to extend the lifespan of this useful plugin 👍