v-shared-element VS router

There is https://github.com/justintaddei/v-shared-element which is close to but not quite the solution I wanted.

You should have a Vue project set up with Vue Router and Vitest. If you haven't done so, refer to this post to set up the essentisal Vitest testing environment for your Vue project.

Flexibility: Vue is also flexible but provides more built-in solutions out of the box, such as Vue Router for navigation and Vuex for state management. This can reduce the need for additional libraries and make development more straightforward.

Let's install Vue.js using Vite. For the router we will use vue-router. For styling we will try the alpha version of the future Tailwind v4 release.

VueJs use vue-router to manage navigation within our apps. Let's create another page and programatically navigate between two pages.

If you would like to learn more about the basic usage of Vue Router, check out the official documentation here.

"src" folder, is the most interesting for us because it is a place where the application source code is typically stored, we will work with this folder in the future and consider its files more detailed. But shortly: "assets" folder contains our global style files, images and icons; the "components" folder as it sounds and will store our app components; "router" and "store" folders were created for "Vue Router" and "Pinia" modules; "views" folder will contain our pages components.

This post assumes you have a Vue project set up wit Vue Router and Playwright component testing. If you haven't done so, please refer to the previous post to set up Playwright with component testing for your Vue project.

Routes tab is a feature integrated with Vue Router, allowing you to view the registered routes and their details.

Whenever I made changes to my component, hot reloading didn't occur, and an error appeared in the console: [hmr] Failed to reload /src/[Component.vue]. This could be due to syntax errors or importing non-existent modules. (see errors above).. To learn more about this error, you can refer to the GitHub issue here.