Beta 49 breaks dev server on case-sensitive systems

[emanguy]

⚠️ IMPORTANT ⚠️ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

• Read the docs.
• Use Vite >=2.0. (1.x is no longer supported)
• If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug

On a fresh npm init @vitejs/app, performing a yarn install installs 2.0.0-beta.49, which causes a breaking error when trying to run the dev server:

It appears to work fine if you run yarn add --dev vite@2.0.0-beta.48.

Reproduction

Repo: https://github.com/emanguy/vite-bug-repro-beta49

Just run yarn install && yarn run dev

System Info

• vite version: 2.0.0-beta.49
• Operating System: Ubuntu 20.04
• Node version: 12.20.1
• Package manager (npm/yarn/pnpm) and version: yarn 1.10.1

Logs (Optional if provided reproduction)

1. Run vite or vite build with the --debug flag.
2. Provide the error log here.

yarn run v1.10.1
warning package.json: No license field
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ vite --debug
  vite:config bundled config file loaded in 158ms +0ms
  vite:config using resolved config: {
vite:config   plugins: [
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'vite:dynamic-import-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:vue',
  vite:config     'vite:css-post',
  vite:config     'vite:client-inject',
  vite:config     'vite:import-analysis'
  vite:config   
],
  vite:config   server: {},
  vite:config   define: { __VUE_OPTIONS_API__: true, __VUE_PROD_DEVTOOLS__: false  },
  vite:config   ssr: { external: [ 'vue', '@vue/server-renderer'  ]  },
  vite:config   configFile: '/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/vite.config.js',
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     server: {}
  vite:config   
  },
  vite:config   root: '/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite',
  vite:config   command: 'serve',
  vite:config   mode: 'development',
  vite:config   isProduction: false,
  vite:config   optimizeCacheDir: '/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/node_modules/.vite',
  vite:config   alias: [
	  vite:config     {
  vite:config       find: /^\/@vite\//,
  vite:config       replacement: '/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/node_modules/vite/dist/client/'
  vite:config     
	  }
  vite:config   
  ],
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge16', 'firefox60', 'chrome61', 'safari11'  ],
  vite:config     polyfillDynamicImport: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     commonjsOptions: { include: [Array], extensions: [Array]  },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     cleanCssOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false
  vite:config   
  },
  vite:config   env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false  },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen]
  vite:config   
  },
  vite:config   base: '/'
  vite:config 
  } +3ms
  vite:resolve 0ms   vue -> null +0ms
Optimizable dependencies detected:
vue
Pre-bundling them to speed up dev server page load...
(this will be run only when your dependencies or config have changed)
  vite:resolve 0ms   @vue/runtime-dom -> null +10ms
  vite:resolve 0ms   @vue/shared -> null +1ms
  vite:resolve 0ms   @vue/runtime-core -> null +5ms
  vite:resolve 0ms   @vue/reactivity -> null +14ms
(node:118886) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/evan/desktop/programming/personalworkspace/webdev/vue/sample-vite/node_modules/vue/dist/vue.runtime.esm-bundler.js'
    at Object.openSync (fs.js:462:3)
    at Object.readFileSync (fs.js:364:35)
    at optimizeDeps (/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/node_modules/vite/dist/node/chunks/dep-dee4e734.js:71322:64)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async runOptimize (/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/node_modules/vite/dist/node/chunks/dep-dee4e734.js:73983:13)
    at async Server.httpServer.listen (/home/evan/Desktop/Programming/PersonalWorkspace/WebDev/Vue/sample-vite/node_modules/vite/dist/node/chunks/dep-dee4e734.js:73996:13)
(node:118886) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:118886) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.