node-zwave-js: yarn install fails on Raspberry Pi because turbo dropped arm support

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

turbo recently dropped its linux_arm target (https://github.com/vercel/turborepo/pull/1903) and thus yarn install fails on the Raspberry Pi:

pi@hass-home:~/devel/node-zwave-js$ yarn
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @zwave-js/cc@workspace:packages/cc doesn't provide jest (p93dff), requested by jest-extended
➤ YN0002: │ @zwave-js/config@workspace:packages/config doesn't provide jest (pf36d7), requested by jest-extended
➤ YN0002: │ @zwave-js/host@workspace:packages/host doesn't provide jest (p78fa7), requested by jest-extended
➤ YN0002: │ @zwave-js/maintenance@workspace:packages/maintenance doesn't provide jest (p84488), requested by jest-extended
➤ YN0002: │ @zwave-js/serial@workspace:packages/serial doesn't provide jest (p3c88c), requested by jest-extended
➤ YN0002: │ @zwave-js/testing@workspace:packages/testing doesn't provide jest (pbf7f4), requested by jest-extended
➤ YN0002: │ zwave-js@workspace:packages/zwave-js doesn't provide jest (pd99e8), requested by jest-extended
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 4s 957ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ typescript@npm:4.8.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ typescript@patch:typescript@npm%3A4.7.4#~builtin<compat/typescript>::version=4.7.4&hash=a1c5e5 can't be found in the cache and will be fetched from the disk
➤ YN0013: │ typescript@patch:typescript@npm%3A4.8.3#~builtin<compat/typescript>::version=4.8.3&hash=a1c5e5 can't be found in the cache and will be fetched from the disk
➤ YN0000: └ Completed in 233m 52s
➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.15.7 must be built because it never has been before or the last one failed
➤ YN0007: │ nice-napi@npm:1.0.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @serialport/bindings-cpp@npm:10.7.0 must be built because it never has been before or the last one failed
➤ YN0007: │ turbo@npm:1.5.2 must be built because it never has been before or the last one failed
➤ YN0009: │ turbo@npm:1.5.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-3869fda1/build.log)
➤ YN0009: │ nice-napi@npm:1.0.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-c17ba418/build.log)
➤ YN0007: │ @zwave-js/repo@workspace:. must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 3m 49s
➤ YN0000: Failed with errors in 237m 49s

# This file contains the result of Yarn building a package (turbo@npm:1.5.2)
# Script name: postinstall

/home/pi/devel/node-zwave-js/node_modules/.store/turbo-npm-1.5.2-45c791897d/node_modules/turbo/node-platform.js:38
    throw new Error(`Unsupported platform: ${platformKey}`);
          ^

Error: Unsupported platform: linux arm LE
    at pkgAndSubpathForCurrentPlatform (/home/pi/devel/node-zwave-js/node_modules/.store/turbo-npm-1.5.2-45c791897d/node_modules/turbo/node-platform.js:38:11)
    at checkAndPreparePackage (/home/pi/devel/node-zwave-js/node_modules/.store/turbo-npm-1.5.2-45c791897d/node_modules/turbo/install.js:252:28)
    at Object.<anonymous> (/home/pi/devel/node-zwave-js/node_modules/.store/turbo-npm-1.5.2-45c791897d/node_modules/turbo/install.js:302:1)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
    at Module.load (node:internal/modules/cjs/loader:1033:32)
    at Function.Module._load (node:internal/modules/cjs/loader:868:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:22:47

Device information

No response

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version: node-zwave-js branch: git master (1989eceb5e0502f6c3171c78ab29b2764eadb59e)

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

Older versions did work on the pi

Attach Driver Logfile

Cannot attach driver log