quickjs-rs VS offscreen-webrtc

Implementing this using quickjs sounds like a great little weekend project. If only I had a weekend to spend on it!

This doesn't look like an issue with rust, what's happened is that a patch file has failed to apply which probably means that the source has been changed since the patch was created. I would open an issue on the mdbook-katex repo with as much information as you can provide, but they will probably point you towards the libquickjs-sys repo because that's where the actual issue is occurring.

Using an extension we can create an offscreen document, connect to a Native Messaging host, stream stdin to a local application, and stream stdout to the browser (Web page), see offscreen-webrtc.

There are multiple ways to upload and send files, including WebRTC datachannels, e.g., https://github.com/guest271314/offscreen-webrtc, WebTransport, WebTorrent https://github.com/jeremyckahn/secure-file-transfer, WebSocket, WebSocketStream, or just using Fetch and Streams. fetch() on Chromium-based browsers also supports duplex:'half' in request init for bi-directional streaming capability.

To achieve this specific task, once an HTML page is loaded into the browser, and a ServiceWorker is registered for that scope, the server does not need to remain active to maintain the functionality of intercepting requests from the Web page (popup window) to the ServiceWorker, where the ServiceWorker can itself make requests to, for example, the same local server to execute parec and pipe output to multiple EventSource responses within the same initial connection, or pipe data to a single ReadableStream served with Response() and event.respondWith(), e.g., see https://github.com/guest271314/offscreen-webrtc, https://github.com/guest271314/sw-transfer-stream.

I've already built it https://github.com/guest271314/captureSystemAudio#web-accessible-resources-transferable-streams-media-capture-transform-breakout-box, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.js; see also https://github.com/guest271314/sw-transfer-stream and https://github.com/guest271314/offscreen-webrtc. I'm just trying to reduce steps https://github.com/guest271314/requestClient.

Yes, you can create an iframe and/or a new window that you have complete control of to execute arbitrary code using either localhost or an extension; e.g., https://github.com/guest271314/sw-transfer-stream, https://github.com/guest271314/offscreen-webrtc.

Yes. You can use WebRTC. See https://gist.github.com/guest271314/53e00c6765aa256362fb52c08e82d189, https://github.com/guest271314/offscreen-webrtc.

Establish WebRTC connection between offscreen document and arbitrary Web page to transfer data from ServiceWorker to Web page https://github.com/guest271314/offscreen-webrtc

There are workarounds which involve using an iframe https://github.com/guest271314/persistent-serviceworker/tree/main/chromium_extension_web_accessible_resources_iframe_message_event or window.open() https://github.com/guest271314/sw-transfer-stream or and offscreen document https://github.com/guest271314/offscreen-webrtc with WebRTC - however that involves loading an entire HTML document, and each has its own deficienfies - with all of the Window features that we do not really need just to transfer data between the Web page I have control of and the ServiceWorker I have control of.