outDir option that has 2 depth throws ENAMETOOLONG error

[ravieeeee]

Describe the bug

outDir option that has 2 depth throws ENAMETOOLONG error.

// vite.config.js
build: {
  outDir: 'public/build',
}

ENAMETOOLONG: name too long, mkdir '/vite-project-name/public/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build/build'

Reproduction

$ vite build

System Info

Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:

System:
    OS: macOS 10.15.7
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 11.31 GB / 32.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.14.0 - ~/.asdf/installs/nodejs/12.14.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.13.4 - ~/.asdf/installs/nodejs/12.14.0/bin/npm
  Browsers:
    Chrome: 90.0.4430.93
    Chrome Canary: 92.0.4489.0
    Firefox: 86.0.1
    Safari: 14.0
  npmPackages:
    vite: ^2.2.3 => 2.2.3

Used package manager: npm

Logs

---

Before submitting the issue, please make sure you do the following

• 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.
• Provide a description in this issue that describes the bug.
• 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.

[patak-dev]

@ravieeeee this is failing because the public dir and the out dir are the same. If you want to use public/build, the publicDir needs to be changed to another directory (or disabled, that is a feature that will be added soon)