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.
Build step-by-step visual instructions by arranging icons on a structured canvas.
Translation pending
ProductivityTypeScript · JavaScriptGitHub @P-LeidelOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
A browser-based, offline-first app for building step-by-step visual instructions by arranging icons on a structured canvas.
Requires Node.js 20+.
Planning and architecture docs live in docs/:Read the full README ↗A browser-based, offline-first app for building step-by-step visual instructions by arranging icons on a structured canvas.
Requires Node.js 20+.
npm install
npm run dev # start the dev server
npm run typecheck # tsc -b, no emit
npm run lint # eslint .
npm run build # typecheck + production build
Planning and architecture docs live in docs/:
The chosen host is Vercel. Use the Vite defaults:
npm cinpm run builddistNo Vercel-specific package, serverless function, or backend configuration is required. The app is deployed as a static client-side build.
See docs/milestones.md for the current phase and task-by-task status - it's the one place that's kept up to date as work lands, so it's deliberately not duplicated here.