fix Windows ARM64 TUI startup when bun:ffi is unavailable

[sudorest]

Summary

On Windows 11 ARM64, the TUI can fail to start with:

This happens before the TUI finishes startup.

Environment

• Windows 11 ARM64
• Parallels Desktop
• MacBook Pro M4 host

Expected

The TUI should still start even if Bun's FFI support is unavailable for the Windows console helper path.

Actual

The TUI exits during startup because the Windows helper eagerly imports .

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Windows ARM64 native: OpenTUI fails to initialize with bun:ffi dlopen TinyCC error #19130: Windows ARM64 native: OpenTUI fails to initialize with bun:ffi dlopen TinyCC error — describes the same environment (Windows 11 ARM64), the same error (bun:ffi dlopen() is not available in this build), and the same symptom of TUI failing to start.

Please review that issue and add any new findings there if the underlying cause or context differs.

[bold84]

I added Windows ARM64 to TinyCC and created a PR:

oven-sh/tinycc#2

This is the bun issue...

oven-sh/bun#28055

Once TinyCC PR is merged, bun:ffi should be available on Windows ARM64.

[johnW-ret]

@bold84 Thank you for looking into this. When do you think it will be merged? Or is there a tiny drop-in or a way to build from source people can use as a workaround in the meantime?

[bold84]

I don't know when or if the maintainer will merge it

[Carson-yy]

I've encountered the same problem. When will it be fixed? Or is there any way to use it? Can a lower version work?

[Hona]

No - bun doesnt work correctly on arm64.
we will be on node soon which will fix this

[Billzhong2022]

I've reproduced same issue. When will you fix it? Please help share ETA to us. Thanks!

[jcompagner]

the original TinyCC already seems to have at least some support for this right? looking at this: TinyCC/tinycc@30afb50