Hysen Labswassgha/rescript: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking wassgha/rescript.
Project scope
wassgha/rescript describes itself in the README as "🎬 Open source, transcript-based video/audio editor that lives in the browser.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Edit video and audio like you edit text , fully offline, on your device.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "Download" section gives a useful starting point for deciding whether the project fits: 📝 Word-level editing , select words, press ⌫, the cut follows the text. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: 🔒 Private by design , no auth, no uploads; all media processing happens on-device. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "Download". The source evidence includes: cut regions, playhead; scroll to zoom, side-scroll to pan. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: npm install # also copies ffmpeg/onnxruntime WASM into public/vendor npm run dev # Next.js web app (http://localhost:3000) npm run electron:dev # Electron shell + Next.js dev server npm run build # production web build npm run dist # unsigned desktop installers into dist/ npm run lint # eslint When the README contains no runnable command, this article does not invent one. Open its "Download" section and confirm system dependencies, default ports, and first-run initialization before using a public server.