txiki.js VS proposal-common-minimum-api

txiki.js

// https://github.com/denoland/deno/discussions/17236#discussioncomment-4566134 // https://github.com/saghul/txiki.js/blob/master/src/js/core/tjs/eval-stdin.js async function readFullAsync(length, buffer = new Uint8Array(65536)) { const data = []; while (data.length < length) { const input = await open("/dev/stdin"); let { bytesRead } = await input.read({ buffer }); await input.close(); if (bytesRead === 0) { break; } data.push(...buffer.subarray(0, bytesRead)); } return new Uint8Array(data); }

I've only dabbled with the shared libraries once, with the help of the owner of the lnked repository. I wound up solving the issue adjusting the code I was working on https://github.com/saghul/txiki.js/issues/294.

I have written the same code in C++ https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.cpp, Python https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.py, and QuickJS (C source code) https://github.com/saghul/txiki.js/issues/294. QuickJS is the only implementation that winds up clipping the end of real-time audio capture.

QuickJS is awesome, simple to use and very easy to integrate.

Over the past few years I slowly built a small JS runtime using QuickJS as the engine and libuv as the platform layer, amongst other things, in case anyone wants to take a look: https://github.com/saghul/txiki.js

If you are considering building a modern JavaScript runtime I would suggest reading Minimum Common API.

Deno, CloudFlare Workerd, VM Labs WASM Worker Server, and others use some semblance of the ServiceWorker onfetch pattern as a server implementation. Why? Because onfetch of a ServiceWorker with Response() used to send a response to the client is ergonomic. Web API's being implemented by JavaScript runtimes that do not target the browser. In order to try to normalize implementation of Web API's for compatibility there is https://github.com/wintercg/proposal-common-minimum-api.

I guess you do not support Minimum Common API even though Node.js does?

Common I/O (stdin/stdout/stderr) module specification #47.

My goal for one part of this project was to use the same fetch() code in a Node.js and Deno Native Messaging host, respectively, in the spirit of Minimum Common API

The premise of this question is precisely why I filed Single HTTPS server for QuickJS, Bun, Deno, Node.js - without reliance on either to build #33. Closed as