If you want to use content inside your public folder, it's easy, you just add a / at the beginning of your path:

<img src='/assets/img/example.png' />

But, if you have located your content inside resources folder, then it becomes a bid tricky.

Imagine your working directory looks something like this :

resources
|____ images
|     |____ map.jpg
|____ js
|      |____ Pages
|            |_____ Test.vue
|
|____ css // its content (not important in this example)
|____ views  // its content (not important in this example)

Then inside your Test.vue file, You normally include your image this way:
(There is a better way which I am going to mention)

<img src="../../images/map.jpg">

First of all when you use multiple '../'s, your path looks ugly, and second of all if in future you decide to relocate your component you have to modify the path again.

So, it's better to define alias. If we add following block inside vite.config.js file, 2 aliases will be defined:

export default defineConfig({
    plugins: [
        ...
    ],
     // ↓↓↓↓ ADD THIS ↓↓↓↓
    resolve: {
        alias: {
            "@": "/resources",
            "@img": "/resources/images",
        },
    },
});

Now that we have added 2 new aliases there are 2 ways to write your path:

First Way

<img src="@/images/map.jpg" />

Second Way

<img src="@img/map.jpg" />

This way, you no longer have to write all those '../'s in your path

I've found this beautiful tutorial: https://medium.com/@andrewmasonmedia/how-to-use-images-with-vite-and-vue-937307a150c0

But for you case I think this is what you want:

<script setup>
import imgUrl from './assets/img.png'
</script>

<template>
  <img :src="imgUrl" />
</template>

One issue that I see is that you are trying to bundle your image asset with an "absolute path": you start the path with a back slash, src="/assets/img/logo.png". As such, it will not be included in the build. You will either want to include the resource yourself in the public file or a file off of public or use a relative path to the resource (not starting the path with a backslash).

Reference: Laravel 10 Documentation #URL Processing

Which states:

URL Processing

When using Vite and referencing assets in your application's HTML, CSS, or JS, there are a couple of caveats to consider. First, if you reference assets with an absolute path, Vite will not include the asset in the build; therefore, you should ensure that the asset is available in your public directory.

When referencing relative asset paths, you should remember that the paths are relative to the file where they are referenced. Any assets referenced via a relative path will be re-written, versioned, and bundled by Vite.

Consider the following project structure:

public/
  taylor.png
resources/
  js/
    Pages/
      Welcome.vue
  images/
    abigail.png

The following example demonstrates how Vite will treat relative and absolute URLs:

<!-- This asset is not handled by Vite and will not be included in the build -->
<img src="/taylor.png">
 
<!-- This asset will be re-written, versioned, and bundled by Vite  -->
<img src="../../images/abigail.png">