node-red / node-red/node-red-nodes
SerialPort on Windows does not worked - bindings.node is not a valid Win32 application.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Which node are you reporting an issue on?
node-red-node-serialport
What are the steps to reproduce?
try install it on Windows machine
What happens?
When I install the node-red-node-serialport it install well, but in the node-red command line occured warning:
runtime.welcome
20 Jan 12:45:29 - [info] runtime.version
20 Jan 12:45:29 - [info] runtime.version
20 Jan 12:45:29 - [info] Windows_NT 10.0.19042 ia32 LE
20 Jan 12:45:32 - [info] server.loading
20 Jan 12:45:33 - [warn] ------------------------------------------------------
20 Jan 12:45:33 - [warn] [node-red-node-serialport/serialport] Error: \?\C:\GreenVIP_Testing\Testing\Node-red\Phase0\node_modules@serialport\bindings\build\Release\bindings.node is not a valid Win32 application.
\?\C:\GreenVIP_Testing\Testing\Node-red\Phase0\node_modules@serialport\bindings\build\Release\bindings.node
20 Jan 12:45:33 - [warn] ------------------------------------------------------
20 Jan 12:45:33 - [info] runtime.paths.settings
20 Jan 12:45:33 - [info] context.log-store-init
20 Jan 12:45:33 - [info] storage.localfilesystem.user-dir
20 Jan 12:45:33 - [warn] storage.localfilesystem.projects.disabled
20 Jan 12:45:33 - [info] storage.localfilesystem.flows-file
FreeMASTER Lite server is running
Listening on port 80
20 Jan 12:45:33 - [warn] nodes.credentials.system-key-warning
20 Jan 12:45:33 - [info] nodes.flows.starting-flows
20 Jan 12:45:33 - [info] nodes.flows.started-flows
I tried to call npm rebuild,
also reinstalled it by command, or by pallete.
and many other thinks but it did not hepled.
What do you expect to happen?
I expect that the UART will worked.
Please tell us about your environment:
- Node-RED version:V1.2.7
- node.js version:v16.13.2
- npm version:8.1.2
- Platform/OS:Windows_NT 10.0.19042 ia32 LE
- Browser:Edge
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the installation on Windows_NT 10.0.19042 ia32 with node-red-node-serialport, then inspect the reported @serialport/bindings build/Release/bindings.node failure. Done means the native binding loads without the warning and the UART can be used through the node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100