-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add N-API support #217
Add N-API support #217
Conversation
} | ||
else if (wcscmp(valueType, L"REG_DWORD") == 0) | ||
{ | ||
uint32_t dwordData = info[4].ToNumber().Uint32Value(); |
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.
This is the only change I made with respect the original behavior: we were using int
, but DWORD is an unsigned integer of 32bits, so using uint32_t
is much more correct.
2fc4bbc
to
d0e09b1
Compare
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.
✨
Update registry.js to support N-API. I basically ran the conversion tool and made changes on top of that.
The bulk of the work was about changing part of the syntax, and removing references to V8 in favor of the new N-API replacements.
I also found we were using the wrong type for
DWORD
values, which could cause issues with high values.