serialport VS usb

Everything works very well, except for one detail: the node-serialport doesn't work in Android+Termux environment. You can't use RS232, MODBUS, RS422, or RS485 !!! See here the open issue,

Strangely enough it does package fine with electron-builder but does not work in dev mode. The same happens when I try to use https://serialport.io/ which is also another module where you could achieve device detection.

We use node-serialport instead of the WebSerial API, since it was only recently that Electron supported WebSerial permission overrides to make things like a 'devices screen' viable. The WebBluetooth APIs are still in a situation where you have to do polling shenanigans to get a full device list. I've found the mutated permissions system leaves a lot to be desired when debugging, whereas the NAPI modules are a lot more straightforward.

It really depends. The stuff I'm doing in this video for example is writing a driver stack for a device called the Bus Pirate. Communication is done over serial (which is easy in node with the serialport library). The bus pirate is a device that allows you to talk to other devices over different protocols, including SPI, I2C, and OneWire (as well as bit banging, where you control some electrical signals directly any way you want using software). So while it's not something you'd do directly in production, you can actually test communication with devices in JS in a fast, iterative, interactive way without having to use a microcontroller. You can actually figure out all of your design decisions there and port your code to the microcontroller later if you're building some kind of embedded system device, potentially saving a lot of time and debugging.

Turns out, there is: https://github.com/serialport/node-serialport/issues/2259

We use node-serialport for USB serial communications. It's included in the transport manager renderer process. The installation guide and docs should be good enough to get you started. Hopefully serialport has prebuilds for the combination of system and electron version you're trying. We had to setup an internal prebuilds system and CDN for our app since we'd often find ourselves ahead of the prebuilt versions for node-serialport. Alternatively you can build from source.

Browser ports can't integrate at OS level, they're intentionally separated today, but given that e.g. Node.js has WebUSB support (https://github.com/node-usb/node-usb), I guess you could make a layer that exposes such Wasm drivers as native to the OS. Could be a fun experiment.

I'd recommend https://github.com/node-usb/node-usb instead of usb-detection, it has hot plug events available and is better maintained. It uses NAPI for its addons so they don't need to be rebuilt per Electron version, and more helpfully, you can run tests in NodeJS and then bundle it for Electron and you don't need to rebuild the module between each.

We use node-usb for USB hotplug detection, and rerun the serial poll, diffing the output with the ID information from node-usb to produce reliable device hinting.

I want to work with usb devices in Go, On linux i just have to install libsub, But on windows i have to install a lot of building tools, some times it doesn't work properly! I just want to install WinUSB drivers like https://github.com/node-usb/node-usb did! (it's a corossplatform usb support on javascript node)