proposal-common-minimum-api VS native-messaging

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

// Bun Native Messaging host // guest271314, 10-9-2022 async function getMessage() { const { promise, resolve } = Promise.withResolvers(); // https://github.com/simov/native-messaging/blob/8e99d2a345ae94426a502d05aa5d57b966f6bc78/protocol.js let messageLength = 0, bytesWritten = 0, input = [];

Does not send messages from host to browser equal or to 65536 length.

In Node.js this code https://github.com/simov/native-messaging/blob/master/protocol.js does this

https://github.com/simov/native-messaging/blob/master/nodejs/example.js#:~:text=Raw,Footer

Yes. You can utilize Native Messaging. See https://github.com/simov/native-messaging.

// Node.js Native Messaging host // https://github.com/simov/native-messaging/blob/master/protocol.js // https://github.com/simov/native-messaging/blob/master/nodejs/example.js // Might be good to use an explicit path to node on the shebang line // in case it isn't in PATH when launched by Chrome process.stdin.on('readable', () => { let input = []; let chunk; while ((chunk = process.stdin.read())) { input.push(chunk); } input = Buffer.concat(input); const msgLen = input.readUInt32LE(0); const dataLen = msgLen + 4; if (input.length >= dataLen) { const content = input.slice(4, dataLen); const json = JSON.parse(content.toString()); handleMessage(json); } });