console VS native-messaging

console is not part of the JavaScript programming language. WHATWG has published Console Standard https://console.spec.whatwg.org/ though console is not defined in ECMA-262.

WHATWG's Console mentions stdout several times, does not mention stdin. Using console.log() in a Native Messaging host does not work, as we are not printing to a TTY. That W.I.P. is not applicable reading stdin at all.

https://github.com/whatwg/console/issues is the link so you can tell them they are wrong.

There are a few others too. My favorite is console.group (and console.groupEnd).

A standard exists on how logging using console should work, but unfortunately not all browsers respect it.

// 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); } });