TreeMap
A free, open-source disk-space visualizer. Squarified treemap, duplicate hunting, disk-full forecasting, and cleanup that only ever moves files to the Trash.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證AI Writing Assistant
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Meridian Flow is a TypeScript-first writing platform for fiction writers managing long-running web serials. The v3 rebuild keeps the full-stack monorepo shape: thin deployable apps, domain packages for shared contracts and persistence, explicit server domains, and repo-level tooling for local dev, CI, smoke checks, and deployment scaffolding.
For setup, see DEVELOPMENT.md. For product context, see PRODUCT.md, DESIGN.md, and the project knowledge base.
Domain runtime lives in apps/server/server/domains/, not in package route handlers. See AGENTS.md for the active layout rules.檢視完整 README ↗Meridian Flow is a TypeScript-first writing platform for fiction writers managing long-running web serials. The v3 rebuild keeps the full-stack monorepo shape: thin deployable apps, domain packages for shared contracts and persistence, explicit server domains, and repo-level tooling for local dev, CI, smoke checks, and deployment scaffolding.
For setup, see DEVELOPMENT.md. For product context, see PRODUCT.md, DESIGN.md, and the project knowledge base.
| Package | Role |
|---|---|
@meridian/contracts | Shared wire types, branded IDs, protocol events, thread DTOs, work/project contracts, interrupt/checkpoint types, and agent metadata. |
@meridian/database | Drizzle schema, migrations, PL/pgSQL functions, and Postgres connection helpers for the Drizzle-backed local/runtime database. |
@meridian/design-tokens | Warm-paper design token package for colors, typography, spacing, and shared primitives. |
@meridian/prosemirror-schema | Shared ProseMirror structural contract for TipTap/Yjs document editing. |
Domain runtime lives in apps/server/server/domains/, not in package route handlers. See AGENTS.md for the active layout rules.
apps/app/ — authenticated writing workspace (TanStack Start + React + TipTap)apps/server/ — Nitro API/WebSocket service: auth boundary, thread endpoints, orchestration, collaboration, packages, billing, storage, and server domainsapps/www/ — public marketing sitepackages/ — shared TypeScript librariestools/ — local dev, CI, deployment, smoke-test, and migration toolingtests/smoke/ — operator-facing smoke checks and browser/manual runbookspnpm install
pnpm dev:infra # start the Postgres Docker container (postgres:16 + pg_bigm)
pnpm bootstrap # create the DB, migrate, apply-functions
pnpm dev
Dev is portless: use pnpm portless:list for live https://*.localhost URLs instead of hard-coded raw ports.
pnpm check
MODEL_PROVIDER=mock pnpm exec tsx tests/smoke/run.ts
pnpm --filter @meridian/server smoke:thread-runtime
Database schema changes are generated by Drizzle in packages/database; local Postgres is a Docker container built from tools/postgres/Dockerfile (postgres:16 plus pg_bigm). Auth is WorkOS AuthKit with app-owned public.users.
Open PRs against main using the repo pull request template and fill every section before merge, writing "None." with a reason where one doesn't apply; tools/ci/check-pr-body.mjs enforces the sections. Every PR keeps the long-term direction in view: Core design decisions names what it settles, and Goal opens with the long-term goal it serves.
Repo-root docs are pointer-oriented. Durable product decisions live in the Meridian knowledge base; local .context/ files capture implementation-near facts that agents should read before changing code.