TreeMap
무료 오픈소스 디스크 사용량 시각화 도구로, 사각형 트리맵·중복 파일 탐색·디스크 가득 예측·정리 시 파일을 휴지통으로만 이동한다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.