tynd start
tynd startBuilds frontend + backend from scratch (cache-hash keyed), then runs the host against the built artifacts. No HMR, no watcher.
When to use
- Reproduce what a release build does without producing an installer.
- Profile production-shaped startup latency.
- Debug when the framework dev server is giving you trouble.
Flags
| Flag | Effect |
|---|---|
--cwd <dir> | Run against a project in another directory |
Global flags: --verbose, --quiet.
Pipeline
frontend build ──▶ cache ──▶ backend bundle ──▶ cache ──▶ launch host- Runs the framework build (
vite build,ng build, …) if cache misses. - Bundles the backend if cache misses.
- Launches the host pointing at the built
dist/andbundle.dist.js/bundle.js.
No pack step — the app runs from the cached artifacts.
Cache
Three keys:
frontendbackendbackend-dev(N/A forstart)
Decisions printed on --verbose. Flush with tynd clean.
Related
tynd dev— with HMR.tynd build— produce a release binary.tynd clean— flush the cache.
Last updated on