Debugging the front-end part in a non-WebView environment
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 111k
- Forks
- 4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 45
Description
I tried to imitated this issuecomment
I am developing a Tauri program using VScode on macOS, and the WKWebview cannot use WebView2‘s --remote-debugging-port.
I have a part that uses tauri-apps/plugin-fs, and this part cannot be debugged in Chrome.
The WebKit debugging experience is terrible, are there any other methods?
Originally posted by @r0yx1e in https://github.com/tauri-apps/wry/discussions/1567
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
Start by reading the linked tauri-docs issue comment and the original wry discussion, then compare the reported WKWebView behavior with WebView2's remote-debugging approach. The issue is complete only when a supported alternative debugging method is identified and its scope is documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop, devtools, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100