Meta details

router5 v7.0.2
node    v12.15.0
npm     v6.13.4
OS Version: 10.0.18363 N/A Build 18363

Correct me if I am wrong, but it appears there is a bug with the canDeactivate lifecycle functions. They don't appear to be getting set when configured.

I narrowed this down to onRouteAdded(route). I manually added code for a if (route.canDeactivate) conditional, and things starting working as expected.

        function onRouteAdded(route) {
            if (route.canActivate)
                router.canActivate(route.name, route.canActivate);
            if (route.canDeactivate)
                router.canDeactivate(route.name, route.canDeactivate);

Let me know if this is correct and I'll try, and try to find some time to submit a pull-request with associated tests.