run in browser tutorial help

[CJP-work-acct]

Hi guys, very impressive project I just really feel like I'm missing something on the "get started to browser" path.

I really don't want any node involved at all, I'm trying to build a browser solution. I started with the four blog posts linked at the top level... they seem a little stale but I was able to get to the point where ffmpeg builds and runs in the browser. Unfortunately I am stuck there with an async or a FS issue, I can't tell what: the ffmpeg run never builds the target file and stalls there. Also the browser throws a modal "input" dialog up as though it's blocked on stdin.

So I am trying to use the more recent code in this tree... How and where do I build a server-ready tree that can just be used by browser? Where is the build step that creates the dist trees?

I did break down and install npm and 'npm install' the ffmpeg package, but that just makes the buried node_module directories. Then when I do 'npm start' in the ffmpeg.wasm/examples/browser/ directory I get a fail on finding /node_modules/@ffmpeg/core/dist/ffmpeg-core.js
(It's looking in /node_modules when npm has installed stuff in ~/node_modules... no other node packages seem to be having this problem... is there a way to force the path discovery)

All this seems super hacky though and I know I must be missing some basic step.

I've got the source tree... how do I "make dist" so to speak...
I want to build ffmpeg itself and publish the minimal set of js and wasm to a server-ready tree and go from there, building my browser app...