尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Next.js 16 frontend for the local research stack. Browser requests always use same-origin /api and /hubs; the Next server proxies them to the backend.
Local builds intentionally do not create standalone output, so next start remains supported.
Set NEXT_STANDALONE=1 only for a standalone build. The Dockerfile does this and supplies its internal backend destination through BACKEND_INTERNAL_URL; this value is server-only and is never bundled as a browser API base URL.檢視完整 README ↗Next.js 16 frontend for the local research stack. Browser requests always use same-origin /api and /hubs; the Next server proxies them to the backend.
npm ci
$env:BACKEND_INTERNAL_URL = "http://127.0.0.1:5197"
npm run build
npm run start
Local builds intentionally do not create standalone output, so next start remains supported.
Set NEXT_STANDALONE=1 only for a standalone build. The Dockerfile does this and supplies its internal backend destination through BACKEND_INTERNAL_URL; this value is server-only and is never bundled as a browser API base URL.
npm run contract:check
npm test
npm run lint
npm run typecheck
npm run build
npm run test:e2e
npm audit --audit-level=high
npm run test:e2e runs Chromium against next start with deterministic mocked/degraded backend responses and fails on uncaught page errors or browser console errors.