Live data from Hacker News

Hacking Tauri for Designer

yujonglee.com

1–6 of 6 posts

Re: Hacking Tauri for Designer

#2
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)

Re: Hacking Tauri for Designer

#3

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_.

Re: Hacking Tauri for Designer

#4

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.

Re: Hacking Tauri for Designer

#5

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_.

I have no idea about timeline, progress, or suitability, but IIUC the Tauri folks are exploring integration with Chromium Embedded Framework:

https://github.com/tauri-apps/cef-rs

https://github.com/tauri-apps/tauri/issues/14963#issuecommen... and following comments

https://github.com/tauri-apps/tauri/issues?q=CEF

Re: Hacking Tauri for Designer

#6

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)

Do you know what is the purpose of the staging build? Not sure why the author requires that flag when building the binary.