nodebox-runtime
sw-transfer-stream
nodebox-runtime | sw-transfer-stream | |
---|---|---|
3 | 6 | |
673 | 1 | |
1.3% | - | |
3.6 | 10.0 | |
5 months ago | over 1 year ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nodebox-runtime
-
Vscode.dev: Local Development with Cloud Tools
Oh I think I found the answer.
> Nodebox is a runtime for executing Node.js modules in the browser.
https://github.com/codesandbox/nodebox-runtime
-
Node on Web. Use Nodejs freely in your browser with Linux infrastructure.
"Nodebox is a runtime for executing Node.js modules in the browser. Why we built Nodebox With sandpack-bundler, we allowed any developer anywhere to instantly create a fast, local, shareable playground inside their browser, without having to wait forever to install dependencies and fight with devtools. This improves the learning, experimentation and sharing experience of client-side JavaScript code." nodebox-runtime
-
[AskJS] Has anybody implemented and compiled ServiceWorker specification to a standalone executable?
There is also https://github.com/codesandbox/nodebox-runtime. However, we can already do that using an iframe or window.open().
sw-transfer-stream
-
How to serve exactly 1 HTML file and 1 JavaScript file, then exit the program?
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.
-
[AskJS] Has anybody implemented and compiled ServiceWorker specification to a standalone executable?
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.
-
Run untrusted code in a Web Worker
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.
-
What chrome extensions are you using in 2023?
Open new window to transfer data from ServiceWorker to arbitrary Web page https://github.com/guest271314/sw-transfer-stream
-
[AskJS] What are the worst case scenarios for programmatically setting arbitrary Web pages (Origins) as Client or WindowClient of a ServiceWorker?
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.
What are some alternatives?
wasmedge-quickjs - A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.
persistent-serviceworker - Persistent ServiceWorker
wasm-workers-server - 🚀 Develop and run serverless applications on WebAssembly
chrome-extensions-samples - Chrome Extensions Samples
wasm-jseval - A safe eval library based on WebAssembly and Duktape/QuickJS.
native-messaging-nodejsNative
run - Safely execute untrusted code with ESM syntax support, dynamic injection of ESM modules from URL or plain JS code, and granular access control based on whitelisting for each JS object.
offscreen-webrtc - Offscreen document <=> WebRTC Data Channel <=> Web page
webhoster - HTTP/HTTPS/HTTP2 Web Hoster
native-messaging-quickjs - QuickJS Native Messaging host
native-messaging-deno - Deno Native Messaging Host
readable-stream - Node-core streams for userland