BaraBin VS vue-router

Vue has a wide range of use cases that span the whole scale of front-end development. We can use it to add a bit of dynamism into an existing web app, such as adding a simple carousel or content that changes on user interaction e.g mouse movements or text input to creating complex web apps such as e-commerce stores with multiple categories and product pages supporting routing, browser-based data storage via Vue's own libraries such as the vue-router and vuex with features such as a cart, external API call requests and so forth.

We run this terminal command to enable our application to use Vue Router.

We’ll also need Vue Router for setting up the course pages.

Version 1 used a single-page layout that's very common among developer portfolios. However, I was struggling to fit more content on the site while retaining fast load times. I gave in and switched to lazy-loaded routes that Vue Router supports. I was originally concerned about the weight that some frameworks and bundlers can cause, but Vite's intelligent bundling enables my site to load so fast that I don't even use a preloader anymore!

I am trying to set query params with Vue-router when changing input fields, I don't want to navigate to some other page but just want to modify url query params on the same page, I am doing like this:

And it’s been fun, I have really enjoyed working with SwiftUI so far. However, navigation was the thing that always bothered me. I have used NavigationView for navigation so far and the fact that everything needs to be defined statically was deal-breaking. Why can’t we have easier navigation like Vue Router and Navigation Compose?

NuxtJS relies on vue-router for most of its routing logic.