Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

`serialport` fails in `win11-vs2022_clang-arm64`

Abierto Apto para principiantes
  • ¿Algo no está bien?
#1,220 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@MikeMcC399 ya está trabajando en esto.

Desde el 28/10/2026.

  • #1221 de @MikeMcC399 — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, node.js
Área
ci-cd, testing

Línea de trabajo

Empieza leyendo la entrada de serialport en lookup.json y el código que aplica skip a platform/arch, para ver cómo se expresaría un skip de Windows arm64. Confirma que la compilación que falla es el paso de node-gyp de @parcel/watcher que invoca llvm-lib.exe, que el skip está pensado para evitar en lugar de corregir. Hecho significa que citgm ya no ejecuta serialport en win11 arm64 mientras que sigue ejecutándose en otros lugares, verificado con la coincidencia de plataforma del smoker.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Situation

serialport fails in citgm-smoker running under win11-vs2022_clang-arm64 in Jenkins. Logs under https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3805/nodes=win11-vs2022_clang-arm64/testReport/junit/(root)/citgm/serialport_v13_0_0/ (collaborator access only).

This is also reproducible in the GitHub Actions runner windows-11-vs2026-arm runner for Node.js versions 22, 24 & 26.

windows-11-vs2026-arm includes Visual Studio Enterprise 2026 with Clang.

Item Status
npm package https://www.npmjs.com/package/serialport
npm status not deprecated
last published 13.0.0 Dec 24, 2024
weekly downloads 220,500
repo location https://github.com/serialport/node-serialport
repo last update to default branch Jan 2, 2026
repo status quiet
repo CI status runs in Node.js 18 - 22 (macos- ubuntu- windows-latest)
lookup version / HEAD HEAD
lookup - skip ppc 390x
lookup maintainer 1 reconbot

lookup.json settings are:

  "serialport": {
    "skip": ["ppc", "s390x"],
    "head": true,
    "tags": "native",
    "maintainers": "reconbot"
  },

Logs

 npm error code 1
 npm error path C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher
 npm error command failed
 npm error command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build
 npm error /LTCG:INCREMENTAL: no such file or directory
 npm error C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(1647,5): error MSB6006: "llvm-lib.exe" exited with code 1. [C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher\build\node_modules\node-addon-api\nothing.vcxproj]
 npm error (node:8452) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
 npm error (Use `node --trace-deprecation ...` to show where the warning was created)
 npm error (node:8452) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error gyp ERR! build error
 npm error gyp ERR! stack Error: `C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\arm64\MSBuild.exe` failed with exit code: 1
 npm error gyp ERR! stack     at ChildProcess.onExit (C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\node-gyp\lib\build.js:203:23)
 npm error gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
 npm error gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:324:12)
 npm error gyp ERR! System Windows_NT 10.0.22621
 npm error gyp ERR! command "d:\\workspace\\citgm-smoker\\node\\Release\\node.exe" "C:\\Users\\lhymbtjceacp\\AppData\\Local\\Temp\\3454ddb9\\serialport\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
 npm error gyp ERR! cwd C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher
 npm error gyp ERR! node -v v24.22.2
 npm error gyp ERR! node-gyp -v v9.4.1
 npm error gyp ERR! not ok
 npm error A complete log of this run can be found in: d:\workspace\citgm-smoker\node\Release\npm-cache\_logs\2026-10-27T02_26_58_372Z-debug-0.log

Suggestion

  • Check with @reconbot if there are plans to extend support in serialport to Windows arm64. GitHub Actions now supports a full set of arm64 runner images for Ubuntu & Windows (macOS was already arm64), so a test / CI environment would be available.
  • Encourage also GitHub Actions CI update in serialport > test.yml to test against currently supported Node.js versions 24 & 26.
  • In the meantime, skip serialport testing in citgm on Windows arm64

Related

https://serialport.io/docs/next/guide-platform-support

https://github.com/nodejs/citgm/issues/991#issuecomment-1742192125

i only officially support max Linux and windows on x64, arm is a very popular usecase but I don't have an easy way to test it.

https://github.com/serialport/node-serialport/issues/3149

Lenguaje dominante
JavaScript
Estrellas
606
Forks
159
Merge medio
2 d 19 h
PR fusionados (30 d)
20

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nodejs/citgm

Todos los issues de nodejs/citgm

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.