-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Suggestion: using new system info crate #8357
Comments
Achieving 100% compatibility with Node.js is not achievable with Deno, nor is it a goal of Deno. What APIs that are critical that are missing where there are use cases where mocking the API isn't feasible? heim is a lot of crates, and haven't gone through all the dependencies yet, and it seems like it is fairly slow development that has slowed, wit the biggest version being downloaded being a beta release. That doesn't feel comfortable having such an "immature" set of a crates in Deno. |
Looking at host::uptime https://github.com/heim-rs/heim/blob/master/heim-host/src/sys/linux/uptime.rs - |
Thanks for letting me know this :) I think I could implement I think I need to look into if other methods could be implemented without additional dependencies. |
I'm -1 on bringing |
Issue
The
sys-info
crate seems that it doesn't provide enough APIs fordeno
anddeno
's node compatibility.I think in this issue (#7774),
Deno.systemCpuInfo
discarded node compatibility because of it.Suggestion
How about using a new crate like heim?
Example
For example, I think the
uptime
function could be implemented by the below code usingheim
This function would be needed to implement node compatibility.
Related issue: #3802.
Notes
If we need another package other than
heim
, I would be appreciated if you let me know.The text was updated successfully, but these errors were encountered: