Open mattxo opened 8 years ago
@mattxo that's good news. I'll make that change ASAP.
there seem to be some concerns with the new router. https://github.com/angular/angular/issues/8972
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 :)
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
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
Ah.. They're tracking it here too https://github.com/AngularClass/angular2-webpack-starter/issues/629
@mattxo have you looked into this further? I heard a rumor that the Angular team was abandoning systemJS for WebPack.
@cmelion I have not, I'm mostly doing SPA's and going strong with "@angular/router": "3.0.0"
The new rc1 router can be used no probs.