0.42.1. CompileError: WebAssembly.compile(): Compiling function #66 failed: Wasm SIMD unsupported @+5368 (older version works!) about homebridge-homeconnect

[thoukydides]

It looks like other projects are seeing the same issue:
https://community.n8n.io/t/error-simd-unsupported-on-docker-n8n-container/42155

… again with undici looking like the culprit.

[ZyroBlue]

fixed for me. Thanks a lot!

[thoukydides]

I cannot reproduce that problem on either my development or production setup.

The only differences between v0.41.1 and v0.41.2 are the project dependencies. Only one of those updated dependencies is used at runtime: undici updated from 6.6.2 to 6.7.0. Its changelog mentions some wasm-related changes, so I suspect that might be the cause.

The only other possibly relevant change is that the version of typescript used to compile this project was updated from 5.3.3 to 5.4.2. However, I don’t see how that could trigger a wasm error since it still only outputs JavaScript.

Of course the problem could be caused by an indirect dependency…

This is going to have to wait until I have time to setup a Raspberry Pi with a configuration sufficiently similar to yours to reproduce the error.

What Raspberry Pi model are you using? Since the error is about SIMD support the problem may be specific to a particular CPU version.

How are you installing/running Homebridge, e.g. native install via npm or a Docker image?

[ZyroBlue]

I figured it wasn’t your plugin specifically, because the changelog implied no such change. But I had nothing else to go on other than “downgrade worked”. Sorry.

HB runs natively on Raspberry Pi Zero W. I use the HB repository install.

[thoukydides]

This is almost certainly due to nodejs/undici#2934, which is fixed by nodejs/undici#2935. Updating to the next undici release should fix it…

[sergey-sc]

same here. uninstall and then install 0.41.1 helps

[thoukydides]

v0.41.3 updates undici from 6.7.0 to 6.7.1, which should remove the requirement for a CPU with SIMD support.