Rotem Dan

From what I searched, `vendor-chunks` is a path used by webpack. In any case, trying to bundle `echogarden` in any form is extremely likely to fail on many places since...

It can't run on the web. It runs in Node.js only. * It uses native `ffmpeg` executables to for codec conversions. Although a WASM version of FFMpeg was included in...

Thanks for reporting. On version `2.0.0`, I switched to using an ESM module for `espeak-ng-emscripten`. This means I had to rewrite how it resolves the data file. The new approach...

Seems like I'm mistakenly taking the first `/` as part of the address, and removing it fro the path. Tried on Ubuntu (WSL): `test.js`: ```js console.log(import.meta.url) ``` ``` node test.js...

Turns out windows doesn't like the prefixing `/` in the path: Trying to read a path like: ``` /C:/Rotem/Development/experiments/pathTest/test.js ``` Gives an error. So now I get why I cut...

I published the fix in `v2.0.2`. I made a basic test and it seems like it works correctly on Windows and on Linux (tested on Ubuntu WSL2).

Thanks a lot! I guess was in a hurry so: ```js if (process && process.platform === 'win32') { ``` Wasn't actually correct. Changed it to: ```js if (typeof process ===...

[`@echogarden/audio-io`](https://github.com/echogarden-project/audio-io) is a separate package developed and released a few weeks ago, which includes 3 native addons that interface with the native audio output on Windows (MME / Wave out),...

The issue should be resolved. (I actually later redid the path resolution all over again, in a more robust way, based on the Windows drive letter pattern, like `file:///x:/`, without...

The processing is currently designed to run on Node.js only. I also mentioned that on [a recent issue](https://github.com/echogarden-project/echogarden/issues/48) where someone tried to bundle the package in a similar way (it...