After replacing

function esbuildOutputFromId(outputs, id, cacheDirOutputPath) {
    const flatId = flattenId(id) + '.js';
    return outputs[normalizePath$3(path$n.relative(process.cwd(), path$n.join(cacheDirOutputPath, flatId)))];
}

by

function esbuildOutputFromId(outputs, id, cacheDirOutputPath) {
    const cwd = process.cwd()
    const flatId = flattenId(id) + '.js';
    const normalizedOutputPath = normalizePath$3(
      path$n.relative(cwd, path$n.join(cacheDirOutputPath, flatId))
    )
    const output = outputs[normalizedOutputPath]
    if (output) {
      return output
    }
    for (const [key, value] of Object.entries(outputs)) {
      if (normalizePath$3(path$n.relative(cwd, key)) === normalizedOutputPath) {
        return value
      }
    }
}

in \node_modules\vite\dist\node\chunks\dep-cff57044.js

If I did the edit correctly.

There is no more the error in the terminal.

However, in this case there is

Uncaught TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".

in DevTools console. The site is not working.

Running from the common folder (not sym-linked) still works ok.

Thanks for testing @AlttiRi! I think we could still merge this one (@bluwy, what do you think?), but I don't know if the use case is common enough to justify the complexity. If this is important to you or others, that would be to work on a PR and see how far we are.

Yeah I think this PR looks good to merge.

However, in this case there is

Uncaught TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".

in DevTools console. The site is not working.

This might be a different warning that was initially hidden by the bug this PR is fixing. We could gradually make the fixes to see what's causing this new issue too.