The advantage of supporting the Serial API is the ability for applications to share code between their Electron and web versions without the need for a polyfill layer. There are existing NodeJS modules for communicating with serial ports, such as node-serialport. The Chromium content layer API for this is SerialDelegate. In addition an application could choose to bypass the permission-based flow altogether and configure Electron to return all available ports in response to a call to (). Applications would have the option of presenting their own UI to the user or automatically selecting a particular port.

When () is called a select-serial-port could be fired with a list of available serial ports and a callback. Proposed SolutionĪ pattern for this already seems to exist for the Web Bluetooth API. As this API requires the user to grant permissions there is some work required on the Electron side before it will be supported. Developers have asked whether this API will be supported in Electron in addition to being available in regular web browsers. There is a prototype implementation being developed inside the Chromium project (by me).

The Serial API is a draft specification from the Web Incubator Community Group. I have searched the issue tracker for a feature request that matches the one I want to file, without success.

I agree to follow the Code of Conduct that this project adheres to.I have read the Contributing Guidelines for this project.

Fsnavigator serial