ES6, webpack and forward compatibility

[Audarth]

Creating a new issue since this is a bit different from #357

There's a number of good projects based around creating an angular 1.5 project that's forward compatible with angular 2 and leverages newer technologies like webpack and ES6.

It might be good to move in this direction, I've already created a bit of a prototype based on this project and it seems to work quite well. the code becomes a lot more modular thanks to ES6 and webpack builds the interface to be less than 1 MB compared to around 2 MB for the current default slush running from serve-prod.

I'll put in a pull request though it's definitely far from complete as I haven't supported the themes, intend to convert all of the code to use es6 syntax and need to clean up a lot of code that's no longer used.

[ryanjdew]

Bumping this. Is this something we can get in? I'd like to start contributing again with other tickets, but it seems that a lot of that work will need to be rewritten if we don't update to an angular version that supports components.

Thoughts?

[grtjn]

I'd love to move forward with this, but wondering how much we would need to do (at minimum) on all related components (ml-search, etc) to make it all work, particularly if you include webpack and all.

Then again, merely upgrading to Angular 1.5, and using components for something shouldn't be difficult. But that is what issue #357 is about. Nish did a first stab at that in the past, but we could do an even shallower start that just upgrades to Angular 1.5 (optionally with polyfill for older Angular)..