I do understand your advice and I agree with them.
However I am not in control of this software I am working on.

Users have angular apps compiled and hosted.
Then they buy our service and include our script on the page as the first script. We work as an apm tool.
Angular app and our script are completely separated, and we have 0 prod dependencies.
Also we have our own rollout mechanism and users can disable injection of our script via UI on demand.
We are working in sprints and users can only use latest version of our software month in the past.

I do get the router instance passed in as a parameter but from a compiled app which is already live in the page.
I am able to subscribe to the router events via `router["events"]["subscribe"](createRouterEventHandler());`
Is there maybe something on the compiled router instance that I could use more in this regards?

If not at least having stringified event as a name is a second option, which is better than only one option.
Event type property would be great if there would be a plan to add that to angular. Would simplify things a lot for us.