i don't think this fixes #1, it's just a bundle

fixing #1 would mean turning on github pages or throwing some .wavs in the readme

@StoneCypher #1 requests a working example. That's what the script does is bundle all assets and produces a WAV file. Did you run the code?
vits-web.wav.zip

The entire point of the issue that I opened is that a product does better when someone doesn't have to download and run it to evaluate the quality

@StoneCypher

The entire point of the issue that I opened is that a product does better when someone doesn't have to download and run it to evaluate the quality

If you run this from a GH Pages you are literally downloading the source code and running the code in the browser.

I put together example/browser-standalone-bundle.js for hackers to hack, developers to develop, in the browser, standalone, no node, no Vite, no TypeScript.

fixing #1 would mean turning on github pages or throwing some .wavs in the readme

Here you go d840dad.

GH Pages published: https://guest271314.github.io/vits-web/

I'll probably add encoding to WebM, MP3, and raw Opus packets using WebCodecs and Media Capture Transform, e.g., https://github.com/guest271314/WebCodecsOpusRecorder, and to a live MediaStreamTrack https://github.com/guest271314/native-messaging-espeak-ng. WAV is lossless but expensive.