-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fix(ext/node): implement uv.errname #20785
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, can you add a test that exercises this function?
I love to see these little compat bugs getting knocked out. Nice work @littledivy. Thank you for the bug report @birkskyum |
@ry , glad to be helpful, I really didn't want to be spammy. Despite being very excited about Deno for years, I haven't been able to let go of Node for a single project, because virtually my entire stack is incompatible. Opening the door towards node compat made me hopeful that this could change, so i decided to screen Deno support for a big part of the landscape I find myself in. I'm quite confident that delivering on these tickets, as well as allowing opt-in to run postinstall for certain trusted npm deps (sharp, puppeteer etc.), would boost adoption in the front end space significantly. |
Fixes #20617