Asset path is wrongly relative to the user’s root not the root of the output when it built on windows system.

[emosheeep]

Describe the bug

I was developing a plugin aims to reflect virtual file into the ouput, but I found there's something wrong with it on windows.

Here is my config where I customize a simple plugin to proxy virtual file fruit/index.html.

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import fs from 'fs'

const virtualFile = 'fruit/index.html'

// https://vitejs.dev/config/
export default defineConfig({
  base: './', // The problem is here.
  plugins: [
    vue(),
    {
      name: 'test-plugin',
      resolveId(id) {
        return id === virtualFile
          ? virtualFile
          : undefined
      },
      load(id) {
        return fs.readFileSync(
          id === virtualFile
            ? 'index.html'
            : id,
          'utf-8'
        )
      }
    }
  ],
  build: {
    rollupOptions: {
      input: virtualFile
    }
  }
})

When I set base to '' or './', the problem occurs. I tried to reproduce it on Mac OS but failed, everything works well.

Reproduction

https://stackblitz.com/edit/vitejs-vite-mhjhr4

Steps to reproduce

Just uses yarn create vite to create a new project on window system and use config provided above to build, you'll get a weird result in which the fruit/index.html looks like:

System Info

System:
  OS: Windows 10 10.0.19045
  CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
  Memory: 9.09 GB / 15.76 GB
Binaries:
  Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
  npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.57)
  Internet Explorer: 11.0.19041.1566

Used Package Manager

pnpm

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.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-mhjhr4 (Open reproduction)

[sapphi-red]

It seems using path.resolve('fruit/index.html') instead of 'fruit/index.html' works as a workaround.

related: #9771, #9793

[emosheeep]

emmm even though, will it be fixed in the future?

[sapphi-red]

Taking a second look, it seems the problem is that you are resolving the id as non-abosolute id. Vite's internal build-html plugin only expects absolute ids.

I'll close this one as a duplicate of #9662.