Importing Asset using new URL(url, import.meta.url) can't resolve '@' alias in dynamic URLs via template literals

[Chains-Z]

Describe the bug

when I importing Asset according to Vite Guide

const imgName = "vue"
const imgUrlAlias = new URL(`@/assets/${imgName}.svg`,import.meta.url).href

I expect imgUrlAlias === 'http://localhost:5173/src/assets/vue.svg'
but what I really get is imgUrlAlias === 'http://localhost:5173/undefined'
if I replace '@/assets/img.png' with './assets/img.png' or '/src/assets/img.png'
I can get the right url 'http://localhost:5173/src/assets/vue.svg'

when I check Source Code from Developer Tools I notice that

const imgUrlAlias = new URL(`@/assets/${imgName}.svg`,import.meta.url).href

is compiled to

const imgUrlAlias = new URL((/* #__PURE__ */ Object.assign({"/src/assets/vue.svg": __vite_glob_0_0}))[`@/assets/${imgName}.svg`], self.location).href;

the assign part Object.assign({"/src/assets/vue.svg": __vite_glob_0_0})) is handled '@' alias correctly
but the index part [`@/assets/${imgName}.svg/`] didn't
I think this may be a bug

Reproduction

https://github.com/Chains-Z/vite-asset-alias-issue

Steps to reproduce

Run npm install followed by npm run dev
You can see that the middle Vue Logo didn't show up
the reproduce code is in App.vue

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700KF
    Memory: 13.07 GB / 31.82 GB
  Binaries:
    Node: 19.4.0 - ~\scoop\apps\nodejs\current\node.EXE
    npm: 9.2.0 - ~\scoop\apps\nodejs\current\npm.CMD
  Browsers:
    Chrome: 111.0.5563.111
    Edge: Spartan (44.22621.963.0), Chromium (111.0.1661.51)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @vitejs/plugin-vue: ^4.1.0 => 4.1.0
    vite: ^4.2.0 => 4.2.1

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 vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

Duplicate of #10597