You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In practice, this means that a broken and abandoned serialport package is a blow to the entire NodeJS ecosystem. It rules out using JavaScript for embedded or IoT development.
That this is a kind of "left-pad" situation in the part of the JavaScript ecosystem that intersects with hardware.
I believe the project should reconsider its plans for the future and possibly bring in new maintainers to continue active development.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone.
This is a very cool and unique project. In fact, it is essentially the only way to use serialport in NodeJS.
Unfortunately, at the moment the project appears to be abandoned:
bindings-cpphave remained unfixed for years, even when there is a one-line PR available. Example: https://github.com/serialport/bindings-cpp/pullsBecause of this, end users are forced to:
Create horrible workarounds, for example:
Or even fork an entire package just to include critical fixes, for example:
In practice, this means that a broken and abandoned serialport package is a blow to the entire NodeJS ecosystem. It rules out using JavaScript for embedded or IoT development.
That this is a kind of "left-pad" situation in the part of the JavaScript ecosystem that intersects with hardware.
I believe the project should reconsider its plans for the future and possibly bring in new maintainers to continue active development.
All reactions