You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
such as I have a real folder C:\Documents\document, then I hardlink it to D:\projects\document(this is a virtal folder now)
if I run npm run dev in D:\projects\document, it throw an error when I open the website
PS > pwd
Path
----
D:\projects\document
PS > npm run dev
> air-duino-document@1.0.0 dev
> vuepress dev docs
✔ Initializing and preparing data- done in 415ms
vite v4.4.7 dev server running at:
➜ Local: http://localhost:8080/
No matching HTML proxy module found from C:/Documents/document/docs/.vuepress/.temp/vite-root/index.html?html-proxy&index=0.js
18:02:14 [vite] Internal server error: No matching HTML proxy module found from C:/Documents/document/docs/.vuepress/.temp/vite-root/index.html?html-proxy&index=0.js
at Context.load (file:///C:/Documents/document/node_modules/vite/dist/node/chunks/dep-3b8eb186.js:37343:27)
at Object.load (file:///C:/Documents/document/node_modules/vite/dist/node/chunks/dep-3b8eb186.js:44211:64)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async loadAndTransform (file:///C:/Documents/document/node_modules/vite/dist/node/chunks/dep-3b8eb186.js:54824:24)
at async viteTransformMiddleware (file:///C:/Documents/document/node_modules/vite/dist/node/chunks/dep-3b8eb186.js:64291:32)
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 vuejs/core instead.
Describe the bug
such as I have a real folder
C:\Documents\document
, then I hardlink it toD:\projects\document
(this is a virtal folder now)if I run
npm run dev
inD:\projects\document
, it throw an error when I open the websiteReproduction
https://github.com/Air-duino/document veupress branche
Steps to reproduce
such as I have a real folder
C:\Documents\document
, then I hardlink it toD:\projects\document
(this is a virtal folder now)if I run
npm run dev
inD:\projects\document
, it throw an error when I open the websiteSystem Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: