-
Notifications
You must be signed in to change notification settings - Fork 187
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
Cannot install on node 10 #84
Comments
On Linux x86_64 with nodejs 10.0.0-1
|
After some tests, it looks like making these two changes solve the problem: File src/BluetoothHciSocket.cpp, change line 276 from File package.json, change line 30 from |
I'm also getting this error and can confirm downgrading to node
|
Any news on this? This prevents a couple of our projects to support Node 10. |
Any progress on this ? Current workaround is:
What is blocking ? I can help on it if needed... Relate-to: WebThingsIO/gateway#1441 |
Any news here? it is very important for all projects that care about full nodejs support or to use current versions! What is so problematic here? |
there's nothing problematic. the maintainer is just not around. |
I've considered forking it, but I haven't wanted to maintain it alone. |
That does sound kinda problematic ;) |
Do you know existing github/npm team that could do co maintenance on this module ? If none may I suggest to move this project to: |
@AlCalzone : i meant there's nothing problematic with the PR itself :) |
I'm also getting this error. |
Thanks!It worked. |
So please vote for: |
Hey All, because also we are very dependent on this library I plan to do the following: I will not accept feature additions, bugfixes we need to see because it's only for the node 10+ compatibility. I still hope that the original library gets a new maintainer that will continue the work or the original maintainer finds time again (no offense). After the release all project that want can change their dep to the new library till the old is reactivated, I post this here to get your opinion or objections against this idea, but we are blocked because of this. So, what do you think? |
I forked it in: Then it could be released in NPM's org subrepo ? |
This fix comes from noble#84 (comment) , so I can't personally vouch for it. Change-Id: Ifde2a3b996ab89a4b12b0eb155c081aca2b11dc3 Origin: https://github.com/jrobeson/node-bluetooth-hci-socket Forwarded: noble#91
@rzr great idea! Thank you for taking the idea over! For NPM release I have no idea whats best. BTW: In theory wealso would need to fork noble the same way because it is used there too and many users are directly using noble ... What do you think? |
@rzr: Who can activate travis/appveyor for this repo so that we still have tests? Or do we need to fix that with own repo forks? |
I activated my travis for: Can you take care of appveyor ? If there are other pendant relevant patches let it know at: Then we'll see how to publish a fixed npm for node10: |
I would need to be in the project to activate appveyor :-( Then you need to ssign me rights/invite me. |
I invited you to join |
Got nothing so far and link shows only that I can not see anything :-) |
@th317erd : are you familiar with node's n-api? It'd be nice to convert the addon to n-api so the module will work across different node versions. We could go with plain C via n-api itself, or C++ via node-addon-api. |
Abandonware namespace was used Update bluetooth-hci-socket for node-10 Relate-to: noble/node-bluetooth-hci-socket#84 Origin: #1 Change-Id: Ib32f0c00bb0e7dcb9a125261cd9db0d11c440c21 Signed-off-by: Philippe Coval <[email protected]>
Issue was just fixed in abandonware#5 :-) |
And released To npm |
npm install @abandonware/noble works for me |
Please also review: Please review open PR to: |
Abandonware namespace was used Update bluetooth-hci-socket for node-10 Relate-to: noble/node-bluetooth-hci-socket#84 Origin: abandonware#1 Change-Id: Ib32f0c00bb0e7dcb9a125261cd9db0d11c440c21 Signed-off-by: Philippe Coval <[email protected]>
Feel free to comment this related ticket: |
May you forward your ticket to downstream version if relevant or confirm @abandonware version match your requirements here: |
You can try this. It works well on my Linux. It has not been tested on other platforms. I hope it will help you. |
(...) In file included from ../src/BluetoothHciSocket.cpp:8:0: ../../nan/nan.h:950:46: nota: se declara aquí NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback( ^~~~~~~~~~~~ ../src/BluetoothHciSocket.cpp: En la función miembro void BluetoothHciSocket::emitErrnoError(): ../src/BluetoothHciSocket.cpp:275:72: error: no matching function for call to v8::Function::NewInstance(int, v8::Local<v8::Value> [1]) Local<Value> error = errorConstructor->NewInstance(1, constructorArgs); (...)
Possibly related to old nan dependency, like is mentioned here:
agnat/node_mdns#210
The text was updated successfully, but these errors were encountered: