尚未检测到更新。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.