Angular-cli: Switch to deprecated router until new router is ready

[wardbell]

The CLI and devs generally should use the deprecated router for now.

The _true_ new router is in development. The RC router (in the @angular/router library) is not release quality and is frozen. The _new_ new router will replace it.

This is a short term road bump.

c/ @hansl

[PascalPrecht]

I agree on this one. Played around with the current rc1 router and it has fewer features than the deprecated one.

[JSMike]

Seeing as there are many options for routers, would it be beneficial to have flags to identify which router blueprint to use? Keep the default as whatever the current @angular/router is, and add flags after that for --router-deprecated --ui-router --ngrx-router etc.?

Edit: Thinking some more about it, it would probably be better to specify this during the init step than every time you go to generate a route, would be better if it was a project variable that gets added to angular-cli.json

[filipesilva]

Closed via https://github.com/angular/angular-cli/pull/992

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}