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

Should we standardize Node's process global? #4

Closed
CanadaHonk opened this issue Jan 22, 2024 · 3 comments
Closed

Should we standardize Node's process global? #4

CanadaHonk opened this issue Jan 22, 2024 · 3 comments
Labels

Comments

@CanadaHonk
Copy link
Member

Should we standardize Node's process global instead of making our own new standardized version?

@littledan
Copy link

We discussed this in a WinterCG call, and while I personally like the idea of reusing the names and rough semantics of existing APIs where it makes sense, it seems that process.argv is not one of these: Node doesn't strip off earlier command-line arguments that are targeting Node itself, and Deno's model of stripping these off is higher-level and preferred. So we should use a new name for this API.

@CanadaHonk
Copy link
Member Author

I think we can close this as not being done with agreement from the WinterCG meeting this week. If someone thinks this should still be done instead, we can reopen.

@ljharb
Copy link
Member

ljharb commented Mar 7, 2024

That doesn't argue against having process itself, just having process.argv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants