Extra forward slash when publicOutputDir setting is blank

[vtt]

Description 📖

When publicOutputDir setting is blank, the resulting URLs have extra forward slash (//) and browser interpretes that as absolute path which is invalid.

Reproduction 🐞

Use the following config/vite.json

{
  "all": {
    "assetsDir": "assets",
    "publicDir": "public",
    "publicOutputDir": "",
    "sourceCodeDir": "app/frontend",
    "watchAdditionalPaths": []
  },
  "development": {
    "autoBuild": true,
    "port": 3036
  },
  "test": {
    "autoBuild": true,
    "port": 3037
  }
}

I did not test setting blank values for assetsDir and publicDir; but I think that they would have the same problem

[ElMassimo]

For a while, the dev server proxy relied on publicOutputDir as a "prefix" to detect requests for the Vite dev server.

Now that Vite has patched bugs related to HMR requests, the proxy can rely on file existence.

I'll consider supporting "publicOutputDir": "", allowing you to have Vite as the only source for frontend assets if that's what you want.

[vtt]

I think the issue here is with publicOutputDir; the documentation does not mention that the value cannot be blank. However, setting a blank value would generate invalid URLs.

[ElMassimo]

Sorry, typo, publicDir => publicOutputDir.