-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
feature request: built-in support for serialport #1546
Comments
Is this a feature request? This stuff lives quite happily already in user-land: https:/voodootikigod/node-serialport Is there a good reason that should change? |
not that happily, but we may need more work in libuv before talking about taking this in to core. @voodootikigod |
I'd rather node/io get proper ability to provide SOCK_OPTS on file descriptors for many reasons not JUST serial port and then serial port can be only JS. |
I don't think serialport should be in core, but I'm 👍 on including the functionality needed to be able to do a userland module in pure JS. |
but isn't this like the entire "websocket support" in core then? |
I'd think using websockets would be somewhat more common than using serialport though. I think it's mostly a concern of if there'd be enough people committed to maintaining it. I'm not firmly against serialport in core, but I'm not convinced it should be there. |
I use IO.js developing desktop software, need access to a lot of serialport-based devices. If I used a third-party module(https:/voodootikigod/node-serialport), It has version matching problem and installation problem ... |
i blame io.js. Chris Williams @voodootikigod http://twitter.com/voodootikigod | GitHub The things I make that you should check out: Help me end the negativity on the internet, share this On Tue, Apr 28, 2015 at 9:01 PM, yrushi75 [email protected] wrote:
|
@yrushi75 the current goal is that within any major-version of io.js, compiled addons should still work regardless of minor and patch version number. We're going to hit 2.0.0 soon which, amongst other things, indicates a need to recompile addons but beyond that you shouldn't need to and if you are then perhaps you could file a bug report so we can look at it. |
I think it easy to interpret a serial port in unix/linux/darwin with module So if you are working under *nix, there is no worry about
|
FWIW: libuv/libuv#19 |
See libuv/libuv#379 |
This will be so great to have built in support of serialport for nodejs! |
Keeping this thread up to date. 379 is closed in favour of libuv/libuv#484. |
Another update: libuv/libuv#484 seems to have good traction. |
It appears that libuv/libuv#484 may have sorta kinda stalled out. If someone with the right skill set is motivated to jump in there and offer to help, that might be A Good Thing.. |
This issue has been inactive for sufficiently long that it seems like perhaps it should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that. (Perhaps N-API will make this less of a pain-point?) |
No description provided.
The text was updated successfully, but these errors were encountered: