-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Rebuild not possible #38
Comments
@rzr would you also mind releasing it? |
you can do it too see history and submit a Release commit it will be released |
Yes you're right ... forgot that :-)) |
@rzr If I would do it I would also upgrade the package-locj file because my dev system is already on npm 8 ... ok? Or would it be an option that you bump it? |
@rzr Any advice? |
npm install --global npm-check-updates |
@rzr it is not about finding updateable deps ... it i about the lock file and the version ... I can do the release PR but then it will have an updated lock file version (alnd also the abve script will not change that). is this acceptable? |
@rzr sorry to bother you again ... if it is ok that I update package lock to npm 8 then I can do the PR ... what's your opinion? |
yea sure try it , and look at history to create a PR to make a new release ! |
I did some nodejs upgrade tests and had bigger issues getting bluetooth-hci-socket rebuilded because by default it simply told
I tried many things and did a bigger research. There is no way to add more parameters to the "nom rebuild" command, so in the end "npm i" would be the only option (with other side effects).
In fact I ended up in adding "--update-binary" to the "install script" and with this a rebuild was successful too ...
The text was updated successfully, but these errors were encountered: