TypeScript / JS Performance
Sources
- Node diagnostics: https://nodejs.org/en/learn/diagnostics
- TypeScript: https://github.com/microsoft/TypeScript
- Web Vitals / browser: use DevTools Performance panel or Chrome DevTools MCP when UI-bound
- Local:
performance-optimizationskill (Addy) for broader checklist
Rules
- Separate Node server vs browser bottlenecks.
- Prefer profiler evidence over “switch library” guesses.
- Keep TypeScript
strictgains; don’t disable checks for speed myths.
Node
node --cpu-prof app.js
node --heap-prof app.js
# clinic / 0x / chrome://inspect as available
npm run build # compare bundle analyzer if frontend
Browser / frontend
- Performance panel: long tasks, layout thrash, LCP/CLS/INP
- React: unnecessary re-renders, list virtualization, memo only when measured
- Network: waterfalls, cache, compression
Checklist
- Repro scenario fixed
- Profile captured (CPU or Performance trace)
- Top cost named with evidence
- Patch + before/after metric
Related
performance-optimizationbrowser-testing-with-devtools/ playwright MCP when UIsource-driven-developmentfor framework docs