No prebuilt binaries found (Alpine)

[MBerka]

Version: tried 12.0.0, 11.0.1, 10.5.0
Arch: x64
Environment: Docker (v. 19.03.8) image "node:18.17.1-alpine"
Host OS: Ubuntu 22.04

I include serialport in x64 and ARM versions of Alpine Docker containers and am used to building everything from source (RUN apk add make gcc g++ python3 linux-headers udev && npm install serialport --build-from-source).

Recent versions of the serialport advertise support for musl, so I am trying to simplify the build process and make sure that the project uses the same standard binaries. However, attempting to replace the above step with just RUN apk add python3 and run

FROM node:18.17.1-alpine
WORKDIR /ts-project
RUN apk add python3 # Replaced
COPY package* tsconfig.json ./
RUN npm ci
COPY src src
CMD ["npm", "run"] # ends up running nodemon

results in:

 => CACHED [project-ts-project 3/6] RUN apk add python3                                                                  0.0s
 => CACHED [project-ts-project 4/6] COPY package* tsconfig.json ./                                                       0.0s
 => ERROR [project-ts-project 5/6] RUN npm ci                                                                           35.2s
------
 > [project-ts-project 5/6] RUN npm ci:
#0 35.07 npm notice 
#0 35.07 npm notice New major version of npm available! 9.6.7 -> 10.0.0
[...]
#0 35.08 npm ERR! code 1
#0 35.08 npm ERR! path /ts-project/node_modules/@serialport/bindings
#0 35.08 npm ERR! command failed
#0 35.08 npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
#0 35.08 npm ERR! prebuild-install warn install No prebuilt binaries found (target=18.17.1 runtime=node arch=x64 libc=musl platform=linux)
[starts build process]

Without the binary, RUN apk add make gcc g++ python3 linux-headers udev is necessary and the full build has to run. Is this expected result (in which case the linked page should mention these dependencies)? Or should target=18.17.1 runtime=node arch=x64 libc=musl platform=linux be finding a binary and skipping the build? This older discussion did something similar with earlier versions but claimed success with the 10.5.0 without going into detail.

[MBerka]

Comments in this issue about prebuilt binaries highlighted the importance of updating all the dependencies, but this has tended to lead to segmentation faults. Returning to the old build versions.