Cannot start empty project on Ramdisk ('vue' is imported but could not be resolved)

[jimmylab]

Describe the bug

Follow the guide from documentation to start an empty vue project:

npm init vite@latest

cd vite-project
npm install
npm run dev

and get errors:

error when starting dev server:
Error: The following dependencies are imported but could not be resolved:

  vue (imported by Z:/vite-project/src/components/HelloWorld.vue)

Are they installed?
    at optimizeDeps (Z:\vite-project\node_modules\vite\dist\node\chunks\dep-972722fa.js:73454:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOptimize (Z:\vite-project\node_modules\vite\dist\node\chunks\dep-972722fa.js:74167:48)
    at async Server.httpServer.listen (Z:\vite-project\node_modules\vite\dist\node\chunks\dep-972722fa.js:74183:21)

Reproduction

See description

btw, all package manager (npm yarn pnpm) failed to run dev server

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 22.48 GB / 31.93 GB
  Binaries:
    Node: 16.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.11 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.21.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 92.0.4515.159
    Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.84)
    Internet Explorer: 11.0.19041.906
  npmPackages:
    @vitejs/plugin-vue: ^1.6.0 => 1.6.0
    vite: ^2.5.1 => 2.5.1

Used Package Manager

npm

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 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.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @jimmylab. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[haoqunjiang]

Z:\? It may also be related to your file system. Is it on a network drive? What shell environment are you using?

I'm not sure but please check that.

[jimmylab]

Sorry for my recklessness, drive Z:\ is a ramdisk, vite behaves well on other drives.

[bluwy]

@jimmylab Hoping to check if this has been resolved? This would be a hard one to fix since it involves one to create a ramdisk to debg it. It would be great if you can help pinpoint where/why Vite fails at this too.

[jimmylab]

Nope. I believe it's related to an issue of node.js:
nodejs/node#6861

[bluwy]

Thanks for the update @jimmylab! That issue seems like it, though I'm not sure what Vite can do here to address the issue, there doesn't seem to be a workaround available currently.

[patak-dev]

Closing, like @sodatea and @bluwy pointed out, there isn't an actionable item here for Vite Core. Thanks for raising the issue though, it is good to have it connected to the upstream issue now.