SPSahil Prasharindevwithsahil.hashnode.dev·2h ago · 17 min readNext.js Explained: Why It Became the Default React FrameworkWhen I first learned React, I thought I had basically learned how to build a frontend. Components. Props. State. Hooks. Routing. API calls. Okay… I can build an application now. Then I tried building 00
SPSahil Prasharindevwithsahil.hashnode.dev·16h ago · 18 min readMastering TypeScript: Interfaces, Generics, Unions ExplainedWhen I first started using TypeScript, I honestly thought it was going to be a lot more complicated than JavaScript. There were types everywhere. string number boolean interface type union generic An00
SPSahil Prasharindevwithsahil.hashnode.dev·17h ago · 18 min readState Management: Context API, Prop Drilling, React.memo, useMemo, and useCallbackThe first time I started building slightly bigger React applications, I didn't really have a state management problem. At least… I didn't think I did. I had a component. The component had some state. 00
SPSahil Prasharindevwithsahil.hashnode.dev·19h ago · 17 min readHow React Works Internally: Virtual DOM, Reconciliation, and RenderingThere was a point while learning React where I started using this: setCount(count + 1); without really thinking about what happens after it. The number changes. The component updates. The screen chan00
SPSahil Prasharindevwithsahil.hashnode.dev·21h ago · 19 min readReact Hooks Masterclass: useState, useEffect, and Custom HooksOne thing that confused me when I started learning React was this: How does a component remember anything? I mean… a component is just a function, right? Functions run. They return something. Then the00
