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
If a directory is present somewhere in the repository where current user does not have read rights, an EACCESS error is shown, and the main.js file will not be served.
The index.html, client, and env.mjs files are served correctly, but main.js is stuck in pending state. If I directly navigate to http://localhost:3000/src/main.js, the source code is served as expected.
This reproduces on both Chrome and Firefox.
Related to #5765, but with different symptoms. I can't tell offhand whether this is a regression, or a new manifestation of the same root cause.
Reproduction
yarn create vite repro --template vue
cd repro
yarn
sudo mkdir private
sudo chmod 600 private
yarn dev
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
Problem
If a directory is present somewhere in the repository where current user does not have read rights, an EACCESS error is shown, and the
main.js
file will not be served.The
index.html
,client
, andenv.mjs
files are served correctly, butmain.js
is stuck in pending state. If I directly navigate tohttp://localhost:3000/src/main.js
, the source code is served as expected.This reproduces on both Chrome and Firefox.
Related to #5765, but with different symptoms. I can't tell offhand whether this is a regression, or a new manifestation of the same root cause.
Reproduction
yarn create vite repro --template vue cd repro yarn sudo mkdir private sudo chmod 600 private yarn dev
Reproduction
See above
System Info
Used Package Manager
yarn
Logs
Validations
The text was updated successfully, but these errors were encountered: