43f8103c5a
Replace Node.js os.freemem() with vm_stat parsing for macOS. The old approach reported ~47.7 GB / 48 GB 'used' because os.freemem() only counts truly free pages, ignoring ~20 GB of inactive/reclaimable cache. New memory breakdown: - App Memory: active + wired + compressor (actual process usage) - Cached: inactive + purgeable + speculative (reclaimable on demand) - Available: free + cached (what apps can actually use) - Pressure: normal/warning/critical based on app memory ratio Dashboard UI updated to show app memory, cached (reclaimable) label, and pressure-based color coding on progress bars. |
||
|---|---|---|
| .. | ||
| public | ||
| src/app | ||
| .gitignore | ||
| eslint.config.mjs | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.mjs | ||
| README.md | ||
| tsconfig.json | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.