Openblock link Error

[TanviSawal]

Expected Behavior:-
Need Hardware to communicate with the GUI which we have designed

Actual Behavior:-
On application when I select the device the ESP 32,needs to be selected

Steps followed:-

1. npm i
2. npm run fetch
3. npm start
4. Next when I select the device ESP32, it shows connecting... And I am getting the Below Error

sysadmin@sysadmin-Default-string:~/openblock-link-main$ npm start

openblock-link@0.2.0 start /home/sysadmin/openblock-link-main
rimraf ../.openblockData/link && node test/start-server.js --log-level=info

Server is ready.
Openblock link server start successfully, socket listen on: http://0.0.0.0:20111
new connection
(node:5929) UnhandledPromiseRejectionWarning: Error: Error: Error: Operation not supported, cannot set
at SerialPort. (/home/sysadmin/openblock-link-main/src/session/serialport.js:162:43)
at SerialPort._error (/home/sysadmin/openblock-link-main/node_modules/@serialport/stream/dist/index.js:76:22)
at /home/sysadmin/openblock-link-main/node_modules/@serialport/stream/dist/index.js:268:25
(Use node --trace-warnings ... to show where the warning was created)
(node:5929) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5929) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Operating System and Browser
e.g. Linux and Google Chrome

Sir
Requesting you to Guide me in the above.