Skip to content
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

Explicitly check for process.geteuid from global scope #916

Merged
merged 4 commits into from
Sep 7, 2023

Conversation

richarddd
Copy link
Contributor

Description of changes:

Windows doesn't have geteuid so import statement will fail running in ESM. We can assume that targets that have geteuid also have process in global scope.

If one or more of the packages in the /packages directory has been modified, be sure yarn changeset add has been run and its output has
been committed and included in this pull request. See CONTRIBUTING.md.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

richarddd and others added 2 commits September 7, 2023 08:35
Windows doesn't have `geteuid` so import statement will fail running in ESM. We can assume that targets that have `geteuid` also have `process` in global scope.
@richarddd richarddd requested review from a team as code owners September 7, 2023 06:45
@trivikr trivikr changed the title Fix invalid windows import Explicitly check for process.geteuid from global scope Sep 7, 2023
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.

5 participants