vercel-labs / vercel-labs/native
Windows bridge ABI mismatch breaks build, dev, ...
Nobody has claimed this yet.
- Dominant language
- Zig
- Stars
- 7.7k
- Forks
- 314
- Avg merge
- 5h
- Merged PRs (30d)
- 13
Description
The Windows WebView2 bridge functions (zero_native_windows_load_window_webview and zero_native_windows_bridge_respond_window) are currently defined inconsistently between Zig and C++ (both sides declare/define them differently). This creates an unclear ABI boundary and is breaking the intended architecture during setup.
Since I am on windows, I would like to work on this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Zig and C++ declarations and definitions of zero_native_windows_load_window_webview and zero_native_windows_bridge_respond_window. Compare their signatures and calling conventions to identify the ABI mismatch. Done means both sides use a consistent boundary and the Windows setup build no longer breaks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, zig
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100