Releases: serialport/node-serialport
Releases · serialport/node-serialport
v4.0.5
v4.0.4
v5.0.0-beta2
Version 5.0.0-beta2 - [all] fixed a crash when pausing while reading thanks to @bminer and @baffo32 and others to debug and fix this - [all] ReadLineParser has been renamed to ReadlineParser to match worldwide convention - [windows] Fix flush behavior using PurgeComm fixing #962 via @samisaham - [windows] Remove read and write timeouts solving #781 via @giseburt - [docs] Electron build docs #965 via @chalkers - [docs] Spelling fixes via @Awk34 - [docs] Update parser docs to be correct #970 via @jacobq - [notes] buffer-indexof is now completely compliant with latest node 6 buffer.indexOf because it's nice to have and we now use it on older nodes - [notes] dropped node 5 support, should still work but you shouldn't use it
v4.0.3
v4.0.2
v5.0.0-beta1
Version 5.0.0-beta1 - `isOpen` is now a property #899 - Allow reopening after an open error #910 - Change parsers to be transform streams #922 - port.path is now read only #898 - Remove lowercased options #898 - Switch to Lie as a promise library (smaller) - [unix] Flush now gives errors and flushes tx and rx #900
v4.0.1
v4.0.0
Version 4.0.0 - Requiring `serialport` now returns the SerialPort constructor function instead of a factory object. `SerialPort.SerialPort` is now depreciated. - `SerialPort` constructor now throws on argument errors immediately. - `.write(writeCallback)` now only calls it's callback once after the entire write operation, it used to be called for each write cycle and return the bytes written. This reduces the number of callbacks by hundreds of thousands over a megabyte at low bandwidth. - Disconnections now always attempt to close the port, and you'll always get a `close` event after a `disconnect` event - All callbacks are called in the context of the port, `this` now equals the port. - Removed `openImmediately` from the constructor's api, the functionality is now named `autoOpen` on the options object. - Removed extraneous flow control settings from the `flowControl` option, use the specific options to set these flags now. - Removed undocumented callbacks from the options object `disconnectedCallback` and `dataCallback` - Renamed `serialportlist` to `serialport-list` - Renamed `serialportterm` to `serialport-term` - Added a contributors guide - Added our first Arduino required integration tests - [unix] `.drain` and `.set` now properly report errors - [unix] Ports are now locked by default with the new `lock` options matches windows default behavior - [windows] `.update()` now supports windows for changing baud rates - [windows] Fixed a bug where we weren't properly opening ports (provides better support virtual com ports too) thanks to @RogerHardiman - [windows] known issue `lock: false` doesn't work (no change in behavior)
v4.0.0-rc1
Version 4.0.0-rc1 - Requiring `serialport` now returns the SerialPort constructor function instead of a factory object. `SerialPort.SerialPort` is now depreciated. - `SerialPort` constructor now throws on argument errors immediately. - Removed `openImmediately` from the constructor's api, the functionality is now named `autoOpen` on the options object. - Removed extraneous flow control settings from the `flowControl` option, use the specific options to set these flags now. - Removed undocumented callbacks from the options object `disconnectedCallback` and `dataCallback` - `.write(writeCallback)` now only calls it's callback once after the entire write operation, it used to be called for each write cycle and return the bytes written. This reduces the number of callbacks by hundreds of thousands over a megabyte at low bandwidth. - All callbacks are called in the context of the port, `this` now equals the port. - Disconnections now always attempt to close the port, and you'll always get a `close` event after a `disconnect` event - Reanmed `serialportlist` to `serialport-list` - Renamed `serialportterm` to `serialport-term` - [unix] `.drain` and `.set` now properly report errors - [unix] Ports are now locked by default with the new `lock` options matches windows default behavior - [windows] `.update()` now supports windows for changing baud rates - [windows] Fixed a bug where we weren't properly opening ports (provides better support virtual com ports too) thanks to @RogerHardiman - [windows] known issue `lock: false` doesn't work (no change in behavior) - Added our first arduino required integration tests - Added a contributors guide
v4.0.0-beta4
- All callbacks now have the port as
this
- Disconnections now always attempt to close the port, and you'll always get a
close
event after adisconnect
event - Removed undocumented callbacks from the options object
disconnectedCallback
anddataCallback
- [unix] Ports are now locked by default with the new
lock
options matches windows default behavior - [windows] known issue
lock
false doesn't work (no change in behavior)