-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Roadmap #746
Comments
My current plans involve a 3.0 release that removes the close and disconnect A 4.0 release will take a bit longer and need some discussion. I want to clean up options, and construor apis (eg throw immediatly on config issues, ensure update does the right thing everywhere. And lastly kill the factory. This will also make it a lot easier to have a single disconnect path for windows and everyone else, and isolate the pause/resume functions to the bindings. |
I put together a shortlist for 4.0 |
I have a few links to serialport like interfaces that could be potential bindings layers.
|
Most of these are completed. Gonna close as 5.0 is close to release. |
I'd like to use this issue to discuss breaking changes to the SerialPort library.
2.0.7
has changed a lot of the internals but left the api largely intact. I'd like to make some goals and address specific api changes.Internals and APi Changes
openImmediately
flag to the port options. #809,chrome.serialport
Support chrome.serialport #739The text was updated successfully, but these errors were encountered: