First off, this is great, and I love that it allowed me to get started with ES6, webpack, and browsersync without previously knowing anything about these. And it got me started writing component-style Angular code, which I would definitely have skipped learning about, if this approach hadn’t made it so easy. Thanks to all involved!
There’s one obvious thing missing, though: there’s no testing library! Do we have a good practice example yet? (At a glance I think this ES6 and component approach is going to make unit testing JavaScript much easier since we’ll be able to unit test most files without having to muck around with Angular hacks. So let’s get people doing this from the beginning.)
Thanks @darius, I agree we absolutely need to have testing set up. I have some (ES6) testing set up in openmrs.js that uses mocha/karma/chai, but we can definitely discuss what we want to use. I’ve created a ticket for that discussion and work here:
Is it cool if I update them to be current with the npm and webpack workflow? It was a little bit tricky getting started doing this as a newbie, and it might save some others some time if the walkthrough is up to date.