🧩 Next Component Analyzer: Stop Guessing if Your Components Should Be Server or Client

Ever added "use client" somewhere in your Next.js app just because "it might need state" — and then wondered a week later? "Wait… does this even need to be a client component?" Yeah… we’ve all been there. This is the story of Next Component Analyzer: the tool built to stop guessing and help you classify components correctly, every time. 🔍 From Developer Pain to Solution Working with Next.js, I noticed a pattern: developers often overuse "use client". Why? They’re not sure if a component uses state or browser APIs They’re following a habit: “Better safe than sorry” A missed "use client" can break hooks or event handlers But overusing "use client" isn’t harmless — it can: Increase bundle size Move server-renderable components to the client unnecessarily Make your project harder to maintain , it wont just appear like that , but it can , you never know. Wanted a way to audit components automatically and answer the question: “Does this component really need to be a client component?” That’