Full-Stack Vue.js 2 and Laravel 5

next
An important feature of navigation guards is that they will halt navigation until
the next function is called. This allows asynchronous code to be executed before
the navigation is resolved: beforeRouteEnter(to, from, next) { new
Promise(...).then(() => { next(); }); }
You can pass false to the next function to prevent a navigation, or you can pass a
different route to redirect it. If you don't pass anything, the navigation is
considered confirmed.
The beforeRouteEnter guard is a special case. Firstly, this is undefined within it
since it is called before the next page component has been created:
beforeRouteEnter(to, from, next) { console.log(this); // undefined }
However, the next function in beforeRouteEnter can accept a callback function as an
argument, for example, next(component => { ... }); where component is the page
component instance.
This callback is not triggered until the route is confirmed and the component
instance has been created. Due to how JavaScript closures work, the callback
will have access to the scope of the surrounding code where it was called:
beforeRouteEnter(to, from, next) { var data = { ... } next(component => {
component.$data = data; }); }