fix(studio): spell the dev server's bun invocation with vite's real path

"bun --bun vite" does NOT keep vite on bun. Measured: it resolves the bare name
to node_modules/.bin/vite and execs that shim, whose shebang is
#!/usr/bin/env node -- so `bun run studio` still produced

  bun --bun vite --host 127.0.0.1
    -> node .../packages/studio/node_modules/.bin/vite --host 127.0.0.1

and dev-mode renders still died on the producer's TypeScript source. Passing the
path directly is what --bun actually applies to.

Verified end to end after the change: `bun run studio` runs as
`bun --bun ./node_modules/.bin/vite --host 127.0.0.1`, and a real 40s / 1200-frame
render of the audio-real fixture (9 audio tracks, two groups) completes through
the studio's own /render endpoint -- 1.28 MB mp4, hasAudio true, no
"Cannot find module .../renderOrchestrator.js".
This commit is contained in:
Vance Ingalls
2026-08-20 16:40:36 -07:00
parent 730f7d4709
commit bbee47cfb1
+1 -1
View File
@@ -45,7 +45,7 @@
"types": "./dist/index.d.ts"
},
"scripts": {
"dev": "bun --bun vite --host 127.0.0.1",
"dev": "bun --bun ./node_modules/.bin/vite --host 127.0.0.1",
"build": "vite build && tsup",
"typecheck": "tsc --noEmit",
"test": "vitest run",