What is TypeScript and How it Extends JavaScript

Most developers add TypeScript to their React projects and keep writing JavaScript. The types are there. Nothing breaks. So they assume they're doing it right. I did this for longer than I'd like to admit. `any` everywhere. Props typed as `object`. useReducer with no idea what shape the state was actually in. Then a production bug showed up that TypeScript should have caught six months earlier. It didn't, because I'd opted out at every hard junction. Here's what actually changed how I think about it: 1. Type your hooks at the boundary, not inside them. `useState<User | null>(null)` tells the component what it's working with before it renders anything. 2. Discriminated unions on state shape. If your component can be loading, error, or success, model it. Don't use three separate booleans and hope for the best. 3. Generic hooks aren't advanced TypeScript. `useFetch<T>` is just a hook that knows what it returns. That's it. 4. `useReducer` without typed actions is a footgun. The reducer is the one place where exhaustive checks pay off immediately. 5. Don't fight the compiler when props get complex. That resistance is the signal, model it properly or the bug will find you in prod. TypeScript doesn't make React harder. Writing React without it just defers the hard part to runtime. Full breakdown in the comments 👇 #reactjs #typescript #webdevelopment

🚨 JavaScript vs TypeScript — The Real Truth “JavaScript is enough… why even learn TypeScript?” -Yeah, I used to think the same 😅 Until I started working on real projects… and reality hit ➣JavaScript (JS): • The backbone of the web • Easy to start, no need to define types • Fast & flexible (sometimes too flexible ) ➮The problem? • Bugs show up at runtime • Code gets messy as it scales Debugging becomes a headache Example: let price = 100; price = "100"; // JS be like: “it’s fine bro” ➣TypeScript (TS): •JavaScript + Superpowers •Adds static typing •Catches errors before your code runs Example: let price: number = 100; price = "100"; // TS: “Not allowed” The Real Difference: •JavaScript → “Run it and see what happens” •TypeScript → “Let me warn you before it breaks” ➣When to use what? •Small project / quick demo → JavaScript • Large project / team work → TypeScript ➣Today’s reality: React, Next.js, Node — all moving towards TypeScript Companies prefer TS for scalable and maintainable code ➣ Final Thought: “JavaScript helps you build fast… TypeScript helps you build right.” #JavaScript #TypeScript #WebDevelopment #MERN #Coding #Developers

I've been writing JavaScript for years. And for years, I thought TypeScript was just extra work. I was wrong. Completely wrong. After switching to TypeScript full-time, my debugging time dropped by almost 40%. My code reviews became faster. Onboarding new devs became easier. And I stopped getting 3am calls about production bugs. Here's everything I wish someone had taught me before making the switch What is TypeScript, really? TypeScript is JavaScript - but with a superpower: a type system. It's a superset of JavaScript, which means every valid JS file is already valid TypeScript. You don't relearn the language. You extend it. TypeScript adds: - Static types (string, number, boolean, custom types) - Interfaces and type aliases - Enums - Generics - Type inference (TS is smart enough to guess types) - Compile-time error checking The TypeScript compiler (tsc) transpiles your .ts files back into plain JavaScript - so browsers and Node.js run it exactly the same. You write safer code. The machine handles the rest. Why JavaScript alone isn't enough anymore in Modern Web Apps JavaScript was built in 10 days in 1995. It was designed for tiny scripts - not 100,000-line enterprise apps, not distributed teams of 50 engineers, not systems that handle millions of users. In JS, this is perfectly valid code: function add(a, b) { return a + b; } add("5", 10); // Returns "510", not 15 No error. No warning. Just wrong behavior at runtime. In TypeScript: function add(a: number, b: number): number { return a + b; } add("5", 10); // ERROR at compile time - caught before it ships This is the core value of TypeScript: it moves bugs from runtime (when users feel it) to compile time (when only you see it).

You know how the TypeScript Type System works? A Big Picture of Type System..... A Static, Structural, compile-time type system. A Static Typescript check the code before running the code. function add(a:number, b:number){ return a + b } const result = add(10, "10") // Here will get an error We use the number type in b, but we passed 10 in quotation marks, which means a string. JavaScript Check = Runtime Typescript Check = Compile Time Type Inference let name = "Josim" // inferred as string let age = 10 // inferred as number //Typescript guesses the type automatically. Now you can say: Typescript guessed automatically - also Javascript Guess dynamically - Why use Typescript? let name = "josim" name = 10 //Javascript replace the name with 10, but typescript throw the error. Structural Type Checking TypeScript doesn’t care about names - it cares about shapes. type User={ name: string age: number } const user = { name: "Josim", age: 20, extra: true } function newUser(user:User){ return user } const result = newUser(user) console.log(result) // Worked //It matches the required structure DO NOT USE any const x // it means any let name:any = "Josim" any === Turning OF Typescript TypeScript builds a “virtual type model” of your code and checks if everything is consistent. Day 2.1 Let me comment on where I should improve my writing #typescript #reactjs #software_engineering #nextjs #mern_stack #best_developer #josim_hawladar

TypeScript or JavaScript for your MVP? Here&#039;s what actually matters for founders who want to move fast and build something that lasts.

Have you ever thought about how TypeScript can improve your JavaScript code? Migrating to TypeScript can feel daunting, but it opens up a new world of type safety and better tooling. ────────────────────────────── Migrating JavaScript to TypeScript Ready to take your JavaScript skills to the next level? Let's dive into migrating to TypeScript! #typescript #javascript #migration #development ────────────────────────────── Key Rules • Start small: Migrate one file or module at a time. • Embrace any errors: They are your friends during the migration! • Leverage TypeScript's any type initially, but aim to replace it with specific types later. 💡 Try This // Example of a simple TypeScript interface interface User { id: number; name: string; } const getUser = (user: User) => { console.log(user.name); }; ❓ Quick Quiz Q: What is the primary benefit of using TypeScript over JavaScript? A: Type safety and better tooling support. 🔑 Key Takeaway Start your TypeScript journey today; your future self will thank you! ────────────────────────────── Small JavaScript bugs keep escaping to production and breaking critical user flows. Debugging inconsistent runtime behavior steals time from feature delivery.

Day 6/100 of JavaScript 🚀 Today’s Topic: JavaScript throughout the years JavaScript has evolved significantly through ECMAScript (ES) versions, improving both syntax and capabilities 📍 ES5 (2009) → Introduced strict mode, JSON support, and array methods like "map", "filter", "reduce" 📍ES6 / ES2015 → Major update with "let", "const", arrow functions, classes, modules, template literals, promises 📍 ES7+ (2016 → present) → Continuous improvements like "async/await", optional chaining ("?."), nullish coalescing ("??"), and more Over time, JavaScript shifted from a simple scripting language to a powerful ecosystem used for: - Frontend development - Backend development (Node.js) - Mobile apps - Desktop apps Another major evolution📈 is the rise of frameworks and libraries: - Frontend → React, Angular, Vue - Backend → Express, NestJS - Full-stack → Next.js, Nuxt.js These frameworks provide structure, scalability, and faster development compared to writing everything from scratch. JavaScript is continuously evolving, and its ecosystem (tools, frameworks, libraries) plays a huge role in modern development Learning core JavaScript is essential before relying heavily on frameworks #Day6 #JavaScript #100DaysOfCode

💡 JavaScript vs TypeScript Which one should you choose? I recently explored the differences between JavaScript and TypeScript to understand better when to use each in real-world projects. As someone building a strong foundation in web development, you wanted clarity on why TypeScript is gaining so much popularity and how it compares with plain JavaScript. Here’s what you learned 👇 🔹 JavaScript - Dynamic typing (flexible but error-prone) - Runs directly in the browser - Great for small to medium projects - Easy to learn and quick to start - But… errors are caught at runtime 🔹 TypeScript - Superset of JavaScript with static typing - Errors are caught during development (compile-time) - Better for large-scale applications - Strong support for OOP (interfaces, enums, etc.) - Improves code readability and maintainability TypeScript doesn’t replace JavaScript it enhances it. For small projects, JavaScript works perfectly. For scalable, team-based projects, TypeScript is a game-changer. This comparison helped me understand how choosing the right tool can improve code quality, reduce bugs, and make projects more scalable. 🤔 What about you? Do you prefer JavaScript or TypeScript for your projects? And why? #JavaScript #TypeScript #WebDevelopment #Programming #LearningJourney

🚀 Day 22 – Understanding the this Keyword in JavaScript If there’s one concept that confuses almost every JavaScript developer at some point… it’s this 😅 But once you get it right, everything starts to make sense 🔥 🧠 The Truth About this 👉 this doesn’t refer to where the function is written 👉 It refers to how the function is called That’s the game changer. ⚡ What I Learned Today ✔️ In objects → this refers to the object ✔️ In regular functions → this is global (or undefined in strict mode) ✔️ In arrow functions → no own this (inherits from parent) ✔️ In event listeners → this is the element 👨💻 Angular Dev Tip If you’ve ever lost this inside setTimeout or callbacks… you’re not alone 😄 👉 Arrow functions are your best friend here: They preserve the component context ✅ 💡 Why This Matters Understanding this helps you: Write cleaner, bug-free code Avoid unexpected behavior Master advanced JS concepts #JavaScript #Angular #FrontendDevelopment #WebDevelopment #100DaysOfCode #LearnInPublic

🚀 How JavaScript Works Behind the Scenes We use JavaScript every day… But have you ever thought about what actually happens when your code runs? 🤔 Let’s understand it in a simple way 👇 --- 💡 Step 1: JavaScript needs an Engine JavaScript doesn’t run on its own. It runs inside a JavaScript engine like V8 (Chrome / Node.js). 👉 Engine reads → understands → executes your code --- 💡 Step 2: Two Important Things When your code runs, JavaScript uses: 👉 Memory Heap → stores variables & functions 👉 Call Stack → executes code line by line --- 💡 Step 3: What happens internally? let name = "Aman"; function greet() { console.log("Hello " + name); } greet(); Behind the scenes: - "name" stored in Memory Heap - "greet()" stored in Memory Heap - function call goes to Call Stack - executes → removed from stack --- 💡 Step 4: Single Threaded Meaning JavaScript can do only one task at a time 👉 One Call Stack 👉 One execution at a time --- ❓ But then… how does async work? (setTimeout, API calls, promises?) 👉 That’s handled by the runtime (browser / Node.js) More on this in next post 👀 --- 💡 Why this matters? Because this is the base of: - Call Stack - Execution Context - Closures - Async JS --- 👨💻 Starting a series to revisit JavaScript from basics → advanced with focus on real understanding Follow along if you want to master JS 🚀 #JavaScript #JavaScriptFoundation #WebDevelopment #FrontendDevelopment #Coding #SoftwareEngineer #Tech