tldr; they wanted to run a Tauri app in browser for dev purposes.
To do so, they shimmed the Tauri’s rust communication bridge to use web-socket to communicate with the main app’s rust implementation.
This is only used by dev, but if something like this is provided by Tauri/Electron it can probably enable a bunch of interesting use cases… (and probably a bunch of RCEs as well, though)
tldr; they wanted to run a Tauri app in browser for dev purposes.
To do so, they shimmed the Tauri’s rust communication bridge to use web-socket to communicate with the main app’s rust implementation.
This is only used by dev, but if something like this is provided by Tauri/Electron it can probably enable a bunch of interesting use cases… (and probably a bunch of RCEs as well, though)
Having built some stuff with Tauri, being able to debug using Chrome instead of a Safari/Webkit console would be _so nice_.
Absolutely not the same thing, but I’m going to shamelessly plug my Tauri MCP in case you find it helpful: https://github.com/hypothesi/mcp-server-tauri
With the debugging capabilities it gives agents, I find I don’t miss Chrome DevTools so much.