Skip to content

fix: windows replace access denied error to EPERM #4067

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

voudin
Copy link

@voudin voudin commented Feb 8, 2025

Fix #3783 #4017

On Windows, accessing a folder without read permissions results in an "access denied" error instead of EPERM.
To ensure consistency across platforms, this error is now replaced with EPERM.

In restricted environments, users may not have permission to read the root folder of the disk.
disk

@voudin voudin force-pushed the fix/access_denied_windows branch 2 times, most recently from edabb77 to 703bada Compare April 6, 2025 12:03
@voudin voudin force-pushed the fix/access_denied_windows branch 4 times, most recently from dc69acb to f384d19 Compare May 14, 2025 20:54
@voudin
Copy link
Author

voudin commented Jun 7, 2025

@evanw, Would it be possible to review this PR when you have a chance?
We've been using this fix on multiple Windows machines to resolve the "access denied" build issue, and it's been working well for us.
Thanks.

fix evanw#3783 evanw#4017
On Windows, accessing a folder without read permissions results in an "access denied" error instead of EPERM.
To ensure consistency across platforms, this error is now replaced with EPERM.
@voudin voudin force-pushed the fix/access_denied_windows branch from f384d19 to be4f880 Compare June 7, 2025 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

esbuild tried to read "../../.." , in vite , using npm run dev
1 participant