can not run dev cmd, when vitesse in pnpm workspace

[kawais]

Describe the bug

I create a pnpm monorepo to install vitesse with these steps:

• git clone git clone git@github.com:kawais/vitessetmp.git
• pnpm i
• cd apps/site
• pnpm run dev

command dev faild with error

> @ dev D:\code\turbo\repo\apps\web
> vite --port 3333 --open

node:internal/modules/esm/load:208
    throw new ERR_UNSUPPORTED_ESM_URL_SCHEME(parsed, schemes);
          ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:208:11)
    at defaultLoad (node:internal/modules/esm/load:103:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:739:12)
    at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:519:43)
    at #createModuleJob (node:internal/modules/esm/loader:543:36)
    at #getJobFromResolveResult (node:internal/modules/esm/loader:312:34)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:280:41)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:582:25) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Node.js v23.7.0

Reproduction

git@github.com:kawais/vitessetmp.git

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD Ryzen 7 7735H with Radeon Graphics
    Memory: 4.92 GB / 15.25 GB
  Binaries:
    Node: 23.7.0 - ~\AppData\Local\fnm_multishells\24360_1742034755615\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.9.2 - ~\AppData\Local\fnm_multishells\24360_1742034755615\npm.CMD
    pnpm: 9.15.9 - D:\code\turbo\repo\apps\web\node_modules\.bin\pnpm.CMD
     when I run "pnpm -v" in cmd, the version is 10.6.3 
  Browsers:
    Edge: Chromium (131.0.2903.146)
    Internet Explorer: 11.0.26100.1882

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

[qianYuanJ]

+1