-
Notifications
You must be signed in to change notification settings - Fork 140
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
Problem with installation #378
Comments
Thank you for your comment. The name this module is registered with on npm is bluetooth-serial-port. Hence the instruction. |
As a matter of fact you are installing a fork of this module. https://www.npmjs.com/package/node-bluetooth-serial-port The repo for that cab be found here: |
Thanks for your quick response. node -v => 16.13.1 I'm wondering what's the right versioning combination of the above? Here's my error:
|
See #309 tl;dr; this module is deprecated and does not support node >= 1.13. Fix may be available in |
@eelcocramer Thank you. I'm trying the branch.
I tried this but it didn't work out. I have never had this error before, to what app is the version referring (93/89)? I guess I need to downgrade a few things. |
This happens when you install the module with one version of node en run it with another version. You should stick with one version for building and running. The master branch (and npm stored code) should work with node 12. |
@eelcocramer |
Just remove and re-install. |
@eelcocramer |
That should be enough when you ran |
Hello.
I've been trying to install this package for days via
npm i
under the title of bluetooth-serial-port which was not successful.After going through days of struggle and almost checking every possible thing, I accidentally noticed that that the name of the repo is in fact node-bluetooth-serial-port but the readme file instructed to use npm i bluetooth-serial-port (the word "node" is missing).
And I guess that was it. A simple name confusion.
If I'm correct, could you please clarify this in the readme to prevent further confusion?
Thanks.
The text was updated successfully, but these errors were encountered: