generator-ng2-webpack Replace router-deprecated

The new rc1 router can be used no probs.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34869347-replace-router-deprecated?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github).

Jun 04 '16 20:06 mattxo

@mattxo that's good news. I'll make that change ASAP.

Jun 04 '16 22:06 cmelion

there seem to be some concerns with the new router. https://github.com/angular/angular/issues/8972

Jun 04 '16 22:06 cmelion

That its undocumented and might change in another release? Thats true, although it's quite usuable in its current form. Whether theres a significant advantage in using or not... I'm not really sure, I don't remember hallelujah moments after switiching. It wouldn't really hurt to wait, I just tend to early adopt :)

Jun 05 '16 06:06 mattxo

I need to get a better handle on how async loading works with the newer router and webpack: https://www.youtube.com/watch?v=d8yAdeshpcw&index=9&list=PLOETEcp3DkCq788xapkP_OU-78jhTf68j

Jun 05 '16 10:06 cmelion

Lazy loading with the new router appears to have a dependency on systemJS and a specific directory structure naming convention that the CLI uses when generating components.

Webpack will require a resolution service plug-in: https://github.com/AngularClass/angular2-webpack-starter/issues/572#issuecomment-219259135

Jun 05 '16 10:06 cmelion

Ah.. They're tracking it here too https://github.com/AngularClass/angular2-webpack-starter/issues/629

Jun 05 '16 10:06 mattxo

@mattxo have you looked into this further? I heard a rumor that the Angular team was abandoning systemJS for WebPack.

Oct 16 '16 12:10 cmelion

@cmelion I have not, I'm mostly doing SPA's and going strong with "@angular/router": "3.0.0"

Oct 17 '16 14:10 mattxo