I really like the proposed change. In fact it's actually exactly what I was doing in my project with the help of extra utility I wrote to be able to more easily compose different guards. The individual guards look exactly as you propose here, with the return that can either contain a route to be redirected to, or false to cancel any further action.

It looks more or less like this:

function authRequired(to, from) {
  if (!isAuthenticated) {
    return { name: routes.ROUTE_LOG_IN };
  }
}

function emailVerificationRequired(to, from) {
  if (!isVerified) {
    return { name: routes.ROUTE_VERIFY_EMAIL };
  }
}

async function orgAccessRequired(to, from) {
  try {
    await checkOrgAccess(to.params.orgId);
  } catch (err) {
    // ...
    return { name: routes.ROUTE_403 }
  }
}

However, in order to keep things even easier to use and understand just by scanning routes file, we implemented ability to compose guards like so:

{
  path: "/dashboard",
  name: routes.ROUTE_DASHBOARD,
  component: () => import("@/pages/Dashboard.vue")
  beforeEnter: composeGuards([
    authRequired,
    emailVerificationRequired,
    orgAccessRequired
  ])
}

So if we return in any guard, none of the following guards will be executed, this way we can create guards that are more easily testable and understanding guards logic is super easy.

I think it might be a good idea to add support for this on the router level too.

Arrays in beforeEnter are already supported in v4 🙂

Nice! Can't wait to start using it and removing the extra logic we have in order to support it :)

It's already possible to write router.beforeEach(() => next(isAuthenticated) IIRC

Edit: I'm not saying I'm not OK with this RFC thought :)

it would become router.beforeEach(() => isAuthenticated)

@posva Yes, I was answering @michalsnik saying he wants to remove extra logic :)

Anyway, your proposal goes further by allowing the return of a Promise 👍

This RFC is now in final comments stage. An RFC in final comments stage means that:

The core team has reviewed the feedback and reached consensus about the general direction of the RFC and believes that this RFC is a worthwhile addition to the framework.
Final comments stage does not mean the RFC's design details are final - we may still tweak the details as we implement it and discover new technical insights or constraints. It may even be further adjusted based on user feedback after it lands in an alpha/beta release.
If no major objections with solid supporting arguments have been presented after a week, the RFC will be merged and become an active RFC.

Rendered

Link should be updated to https://github.com/vuejs/rfcs/blob/master/active-rfcs/0037-router-return-guards.md