Update bitbox-api from 0.2.1 to latest version

[TaprootFreak]

Description

The bitbox-api dependency is severely outdated (v0.2.1, current: v0.12.0).

Known bug in v0.2.1

ethSupported() incorrectly calls wasm.pairedbitbox_cardanoSupported instead of pairedbitbox_ethSupported, returning false for Multi editions that do support ETH. This bug persists through at least v0.12.0.

Workaround in place: The code now attempts ETH operations directly instead of relying on ethSupported() (see bitbox.hook.ts).

Blocker for upgrade

v0.12.0 uses ESM module resolution (./webhid without .js extension) which is incompatible with the current Webpack/react-app-rewired setup. Upgrading requires either:

• Configuring Webpack to resolve extensionless ESM imports (via config-overrides.js)
• Or migrating the build tooling (e.g. to Vite)

Upstream issue

The ethSupported() WASM binding bug should be reported to BitBoxSwiss/bitbox-api-rs.

[davidleomay]

Investigation Summary

Attempted to update bitbox-api from v0.2.1 to v0.12.0. The update fails due to ES module resolution issues.

Root Cause:

The newer bitbox-api versions use "type": "module" and wasm-bindgen. The import path ./webhid (without .js extension) is embedded inside the compiled WASM binary (bitbox_api_bg.wasm), not just in the JavaScript glue code.

$ strings bitbox_api_bg.wasm | grep webhid
./webhid

What we tried:

• Webpack fullySpecified: false in module rules ❌
• Webpack resolve.byDependency.esm ❌
• Patching bitbox_api_bg.js via patch-package ❌
• Disabling webpack snapshots ❌

None of these work because the import originates from the WASM module itself during webpack's resolution phase.

Blocked until:

• Upstream fix in bitbox-api - needs to rebuild WASM with proper .js extensions in wasm-bindgen output
• OR migration to Vite (which handles ESM resolution differently)

Workaround: Stay on v0.2.1