Assets folder alias only working for built-in components

[enricoKoschel]

I have a problem with Quasar v2 (project using Quasar CLI and @quasar/app-vite).

Let's say I want to access the image src/assets/test.png. Using a q-img (or normal img) this works perfectly fine:
<q-img src="~assets/test.png" />

But as soon as I use a component that I wrote like this:
<q-img-test src="~assets/test.png" />
the browser tries to access the literal path ~assets/test.png and the image fails to load.

If I name my own component q-img, the path can get resolved but as soon as I rename it, the path cannot be resolved anymore.

I tried to use the path src/assets directly without the ~, but there I get an issue with Vue Router. It only works on some routes, for instance on the base route (/) or the /about route. There the resolved path is src/assets as expected.
On other routes (like /movie/543), the resolved path changes to movie/src/assets and the image cannot be found anymore.

I also tried to use the public folder, but there the same Vue Router issue occurs.

I have been googling, searching through github issues, Quasar documentation and Stack Overflow for the last 2 hours and I dont know what to do anymore.

I would appreciate it if someone could help me out. Thanks!

[enricoKoschel]

I have found a workaround on this page https://vitejs.dev/guide/assets.

Importing the image like so import image from 'assets/test.png'; seems to work fine on all routes and components.