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
Getting the error shown below on launch.
I found the cause - it happens if the project path contains spaces. Not sure how to resolve the issue though. I guess Vite cannot resolve non-encoded URLs containing characters like %20
Error:
[vite] Internal server error: The request url "E:/vite%20electron/vite-electron-builder/node_modules/.vite/vue.js.map" is outside of Vite serving allow list:
- /E:/vite electron/vite-electron-builder
Refer to docs https://vitejs.dev/config/#server-fs-allow for configurations and more details.
at ensureServingAccess (E:\vite electron\vite-electron-builder\node_modules\vite\dist\node\chunks\dep-24231913.js:64798:15)
at viteServeRawFsMiddleware (E:\vite electron\vite-electron-builder\node_modules\vite\dist\node\chunks\dep-24231913.js:64765:13)
at call (E:\vite electron\vite-electron-builder\node_modules\vite\dist\node\chunks\dep-24231913.js:53749:7)
at next (E:\vite electron\vite-electron-builder\node_modules\vite\dist\node\chunks\dep-24231913.js:53693:5)
at viteTransformMiddleware (E:\vite electron\vite-electron-builder\node_modules\vite\dist\node\chunks\dep-24231913.js:65004:28)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
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.
Describe the bug
Getting the error shown below on launch.
I found the cause - it happens if the project path contains spaces. Not sure how to resolve the issue though. I guess Vite cannot resolve non-encoded URLs containing characters like
%20
Error:
Reproduction
Clone repo to path containing spaces:
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: