尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Free online karaoke with friends. Pick a song, start a party, and sing together in real-time with pitch scoring.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Free online karaoke with friends. Pick a song, start a party, and sing together in real-time with pitch scoring.檢視完整 README ↗Free online karaoke with friends. Pick a song, start a party, and sing together in real-time with pitch scoring.
/prerendered volume), legacy /{lang}/… and slug URLs get 301sRequires Bun >= 1.2.
bun install
bun run dev
Dev server starts on localhost:3001, proxying API requests to the backend at localhost:3000.
| Command | Description |
|---|---|
bun run dev | Start Vite dev server |
bun run build | Production build to build/ |
bun run preview | Preview production build locally |
bun run test | Run tests (Vitest) |
bun run test:e2e | Playwright end-to-end tests (needs the backend on :3000) |
bun run test:stress | Many-singer stress test, see below |
bun run test:stress puts a dozen singers into one party: real Chrome contexts
with a fake microphone, each running the whole pipeline (AudioWorklet → ONNX
pitch worker → WebSocket), the first one hosting. Every browser carries an
in-page monitor, and the run ends with a per-client table (frame rate, long
tasks, JS heap, notes in/out, latency) plus assertions that nobody
disconnected, everyone is on the scoreboard, the singers' notes reached the
host and the host stayed above MIN_FPS. Past eight singers the server puts
only eight on screen (three top scores pinned, five lanes rotating one per
lyric line), so from then on the host hears the lanes rather than everyone,
and the run prints who they were.
| Env | Default | Meaning |
|---|---|---|
REAL_SINGERS | 12 | Chrome contexts (incl. the host) |
BOT_SINGERS | 0 | extra synthetic singers driven from Bun over WebSocket (e2e/wsSinger.js), cheap enough for dozens |
STRESS_SECONDS | 30 | how long everyone sings |
MIN_FPS | 20 | host frame-rate threshold |
CPU_THROTTLE | 1 | DevTools-style CPU slowdown for every real browser: 4 ≈ mid-range phone, 6 ≈ an old low-end one |
Serve the production build for realistic numbers (bun run build && bunx vite preview;
the test reuses whatever is on :3001), because React's development runtime
alone dominates a profile. Emulating an old phone with a dozen singers:
REAL_SINGERS=1 BOT_SINGERS=11 CPU_THROTTLE=6 bun run test:stress.
Mind what you are measuring: every real context runs its own ONNX pitch
worker and YouTube player, so a dozen of them on one laptop saturate the CPU
and every client (host included) stalls — the run then prints a warning that
the host video stopped advancing. That measures the machine, not the app. To
measure the frontend's cost of rendering many singers, keep the real
browsers few and add bots: REAL_SINGERS=2 BOT_SINGERS=40 bun run test:stress.
docker build -t singspree-fe .
docker run -p 80:80 singspree-fe
Multi-stage build: Bun 1 Alpine for bun install --frozen-lockfile && bun run build, then Nginx Alpine to serve the static files. The build stage is deliberately not cached in CI -- installing takes about eight seconds, and caching it meant pulling a 577 MB node_modules layer out of the GitHub Actions cache first.
src/
components/ UI components (MusicBars, Lyrics, ShareCard, ...)
logic/ Pitch detection, mic input, lyrics parsing, WebSocket handling
pages/ Route pages (Entry, Party, Join, compliance pages)
i18n/locales/ 21 locale JSON files
index.css Tailwind v4 theme (neon-cyan, neon-purple, neon-magenta, neon-green)
MIT