native-messaging-espeak-ng VS proposal-temporal

I'm just trying to use coqui-ai/TTS so I can stream speech synthesis output to the browser as I do with eSpeak NG https://github.com/guest271314/native-messaging-espeak-ng. I think the issue has been brought up before on GitHub. I have not read a solution. I am ready to try again if you can suggest a minimal build process.

You can use a Native Messaging host to run local code controlled from the browser. See native-messaging-deno for a general purpose and extensible solution and deno-server where Deno's serveTls is dynamically started to run a local application, stream stdout from the application to the browser, then stop the local server.

A single page Deno server can be found here https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js. I have used this source code // https://github.com/chcunningham/atomics-post-message/blob/main/server.js, renamed to server.msj modified to use Ecmascript Modules instead of CommonJS, e.g.,

I've already achieved the requirement multiple ways, already; from using Native Messaging https://github.com/guest271314/native-messaging-espeak-ng, to using GNU Core Utilities tail, to Deno.watchFs() https://github.com/guest271314/fs, et al., see captureSystemAudio. The one approach I have not yet achieved is compiling to Emscripten - with SSML support.

Create a self-signed certificate. If you are on Chromium or Chrome launch with --ignore-certificate-errors-spki-list=.... Read this https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py#L42-L72. This is how I use HTTPS for Deno and Node local servers and WebTransport https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server.

I use the source code for Deno's serveTls https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js and wrote a Web server module for QuickJS https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

This https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server is what I do using Deno

I created https://github.com/guest271314/native-messaging-espeak-ng which provides a means to send text or SSML to the eSpeak NG speech synthesis engine and parse the generated WAV in the browser. That bypasses waiting around another N years for Google to prioritize Web Speech API, which I see no evidence of Google doing - except for its cloud service.

I merely read the article to see how the author was implementing "Text-to-Speech"; how they implemented "Text-to-Speech"; e.g., native-messaging-espeak-ng to overcome or avoid the multiple issues and limitations with using the specified Web Speech API in the browser.

Even with the initial pitfalls of JavaScript dates, the ecosystem managed to tackle those challenges with good libraries. Some use the native JavaScript date while others have instead created their own robust tools to make up for the quirks JavaScript dates might have. With the JavaScript Temporal API about to roll out, working with dates and time in JavaScript will only improve.

Temporal API

In the TypeScript/JavaScript world the only thing called "Temporal" that I was aware of is the Stage 3 proposal for an excellent new date and time module:

https://tc39.es/proposal-temporal/docs/

Time Zone Canonicalization: Stacked on Temporal to improve handling of changes to the IANA Time Zone Database.