angular 1 component router backporting status?

[alanpurple]

As far as I know Angular 1 component router is being backported from angular2 router

Is it still happening?

release date?

Is it a part of angularJS 1.6 ?

[Narretz]

Backporting depends on the status of the angular2 router. We will discuss this next week internally if we find the time at Angular Connect.
It'll be 99% not be part of 1.6, though. It's possible that it won't be bound to the usual Angular 1.x release, but that's not decided yet.

[alanpurple]

@Narretz Thanks you for the information, I had to decide what to use for routing

[dpogue]

It's been over 2 years since http://angularjs.blogspot.ca/2015/02/preview-of-new-angular-router.html and the new router was touted as the official upgrade path at ng-conf, and we still don't have a working, supported, or maintained Component Router for Angular 1 😒

[alanpurple]

@dpogue
I've stopped waiting for this and decided to use angular-ui-router 1.0.0-rc.1

[bertyhell]

What is the status of backporting the angular router (v4.x) to angularjs (v1.x)?
Is this still on the roadmap or should we stick with ui-router for our angularjs apps?

We're looking at migrating to angular 4, and switching the router would be a nice first step.

[Narretz]

There are no plans at the moment so it's unlikely to happen at all at this point.

[bertyhell]

ok, thx for letting me know.
I'll just update the the latest version of ui-router
and investigate a migration path to angular 4 at some later date

[Narretz]

This is not gonna happen. The complexity was simply to high, and we're moving to LTS in July.