Vite doesn't transform new URL( "/src/assets/") in production build

[Topograph]

Describe the bug

instead of this:

new URL("../../../../assets/images/books/book1/de/Cover_00.jpg", import.meta.url)

i would like to use this

new URL("/src/assets/images/books/book1/de/Cover_00.jpg", import.meta.url)

or even better use a @/ alias for the src directory.

in development mode both versions work while for production only the first variant will get transformed, while /src points to C:/src or whatever file system you`re in.

In the documentation it is stated that

During the production build, Vite will perform necessary transforms so that the URLs still point to the correct location even after bundling and asset hashing.

Is /src.. not considered a relative path, or is this a bug?

Edit 2021.08.02: I think i narrowed the problem down while trying to create a reproduction setup. Sorry for being too lazy to do this earlier.
I think the problem has to do using the imported URLs in a computed variable. (see HelloWorld.vue: 23) and has NOTHING to do with weather the URL starts with / or ./ or whatever.

Reproduction

Link to github repo: https://github.com/Topograph/vite-issue-4416-reproduction

Reproduce issue #4416 like this

1. npm install

2. npm run dev

3. see http://localhost:3000/ and you should see 4 images. toggling the "greyscale" button changes the image sources

4. npm run build or npm run serve to inspect production build

5. open the production build in a browser. you should see, that

   a. Not all assets have been exported (assetsInlineLimit is set to 0, in order to avoid inlining images.)

   b. There is an error in the developer console. following it in the production js (dist/assets/index.*.js) you will see, that not all the new URL("") paths have been correctly transformed

### System Info

```shell
System:
    OS: Windows 10 10.0.19041
    CPU: (16) x64 AMD Ryzen 7 1700X Eight-Core Processor
    Memory: 1.99 GB / 7.95 GB
  Binaries:
    Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 92.0.4515.107
    Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.55)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    @vitejs/plugin-vue: ^1.2.5 => 1.2.5
    vite: ^2.4.2 => 2.4.2

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

[dejour]

could you provide a reproduction repo.

[github-actions]

Hello @Topograph. Please provide a minimal reproduction using a GitHub repository or codesandbox. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[Topograph]

hi! sorry for being lazy- it took some me some time to figure out, how i could reproduce my issue in a simple project. i created a project and linked the github repo. Following the steps in the README.md should make the error clear.

https://github.com/Topograph/vite-issue-4416-reproduction