Standing upstream-requirement issue. Filter: upstream.
Gated feature. Mesh transport on Windows. Windows nodes currently run LAN-only: the native iroh layer cannot be built there, so status().mesh reports unavailable and ticket()/pair() throw MeshUnavailableError (docs/node/troubleshooting.md).
Upstream requirement. The *-gnu build path for the napi module needs a libnode.dll import library that the upstream toolchain ships only for msvc. Unblocks via either the toolchain shipping the gnu import library or our build moving to an msvc target for Windows.
On pin bump / toolchain review. Re-attempt the native/iroh-js Windows build. When it links: add the target to the prebuilt pin set and release matrix, run the tunnel suite on Windows CI, and update the platform matrix in docs/node/beyond-the-lan.md, self-host-a-sync-node.md, and troubleshooting.md. This is the last platform-matrix gap besides arm64 Linux (tracked separately, #118).
Standing upstream-requirement issue. Filter:
upstream.Gated feature. Mesh transport on Windows. Windows nodes currently run LAN-only: the native iroh layer cannot be built there, so
status().meshreportsunavailableandticket()/pair()throwMeshUnavailableError(docs/node/troubleshooting.md).Upstream requirement. The
*-gnubuild path for the napi module needs alibnode.dllimport library that the upstream toolchain ships only for msvc. Unblocks via either the toolchain shipping the gnu import library or our build moving to an msvc target for Windows.On pin bump / toolchain review. Re-attempt the
native/iroh-jsWindows build. When it links: add the target to the prebuilt pin set and release matrix, run the tunnel suite on Windows CI, and update the platform matrix indocs/node/beyond-the-lan.md,self-host-a-sync-node.md, andtroubleshooting.md. This is the last platform-matrix gap besides arm64 Linux (tracked separately, #118).