-
Notifications
You must be signed in to change notification settings - Fork 23
[ Fix ] Os.arch should be a function
#34
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
Conversation
TheSpyder
left a comment
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.
Good catch!
|
I was thinking your lockfile change looked wrong and CI confirms. You've used an old version of yarn. |
|
Ah, whatever you did with the install it upgraded packages as well. I couldn't see before with the scale of the lockfile change. The |
|
Sorry but what should I do? |
|
Either merge main into the branch or rebase it. I might have time soon if you can't figure it out! |
|
Hope that I'm doing it right! |
|
It could be partly my fault for not enforcing yarn's frozen lockfile setting. I might be able to adjust it before merge. |
|
I'm not sure what you did wrong - quite possibly the |
The binding of
Os.archshould have beunit => stringrather than juststring, as seen in https://nodejs.org/docs/latest/api/os.html#osarch