5 JavaScript Tricks That Will Surprise You

🚀 JavaScript Array Methods – Simple Guide If you’re working with JavaScript (especially in React), mastering array methods is a must. Here’s a quick breakdown 👇 ✨ filter() – returns a new array with elements that match a condition ✨ map() – transforms each element into something new ✨ find() – gives the first matching element ✨ findIndex() – returns index of the first match ✨ fill() – replaces elements with a fixed value (modifies array) ✨ every() – checks if all elements satisfy a condition ✨ some() – checks if at least one element satisfies a condition ✨ concat() – merges arrays into a new array ✨ includes() – checks if a value exists in the array ✨ push() – adds elements to the end (modifies array) ✨ pop() – removes last element (modifies array) 💡 Tip: Use map & filter heavily in React for rendering and data transformation. Clean code + right method = better performance & readability 🔥 #JavaScript #ReactJS #WebDevelopment #Frontend #Coding #Developers :::

Day 4 ⚡ JavaScript Promise Methods — Quick Guide If you're working with async JavaScript, knowing these Promise methods can level up your coding and interviews 🚀 🧠 1. Promise.all() 👉 Runs all promises in parallel 👉 Fails if any one fails Promise.all([p1, p2, p3]) .then(res => console.log(res)); 🟡 2. Promise.allSettled() 👉 Waits for all promises (success + failure) Promise.allSettled([p1, p2]) .then(res => console.log(res)); 🏁 3. Promise.race() 👉 Returns the first completed promise Promise.race([p1, p2]) .then(res => console.log(res)); 🥇 4. Promise.any() 👉 Returns the first successful promise Promise.any([p1, p2]) .then(res => console.log(res)); 🔧 5. Promise.resolve() 👉 Creates a resolved promise Promise.resolve("Done"); ❌ 6. Promise.reject() 👉 Creates a rejected promise Promise.reject("Error"); 🧠 Quick Tip: Use all → when all must succeed Use allSettled → when you want all results Use race → fastest result Use any → first success 💡 One-line takeaway: 👉 Choose the right Promise method based on how you want async tasks to behave #JavaScript #WebDevelopment #Frontend #Coding #100DaysOfCode

🚀 JavaScript Array Methods - Simple Guide If you're working with JavaScript (especially in React), mastering array methods is a must. Here's a quick breakdown 👇 ✨ filter() - returns a new array with elements that match a condition ✨ map() - transforms each element into something new ✨ find() - gives the first matching element ✨ findIndex() - returns index of the first match ✨ fill() - replaces elements with a fixed value (modifies array) ✨ every() - checks if all elements satisfy a condition ✨ some() - checks if at least one element satisfies a condition ✨ concat() - merges arrays into a new array ✨ includes() - checks if a value exists in the array ✨ push() - adds elements to the end (modifies array) ✨ pop() - removes last element (modifies array) 💡 Tip: Use map & filter heavily in React for rendering and data transformation. Clean code + right method = better performance & readability #JavaScript #ReactJS #WebDevelopment #Frontend #Coding #Developers

"JavaScript is single-threaded… but still handles async tasks?" 🤯 This is where the Event Loop comes in 🔥 Let’s understand it simply 👇 🔹 JavaScript is single-threaded It can do one task at a time using the Call Stack. 🔹 So how does async work? Thanks to: - Web APIs 🌐 - Callback Queue 📥 - Event Loop 🔁 💻 Example: console.log("Start"); setTimeout(() => { console.log("Async Task"); }, 0); console.log("End"); 👉 Output: Start End Async Task 🔹 Why this happens? - "setTimeout" goes to Web APIs - Then moves to Callback Queue - Event Loop waits for Call Stack to be empty - Then executes it 🚀 Pro Tip: Even "setTimeout(..., 0)" is NOT immediate. 💬 Did this surprise you the first time you learned it? 😄 #javascript #webdevelopment #mern #coding #developers

🔍 JavaScript Quirk: == vs === (this will surprise you) Most devs say: 👉 “Always use ===” But do you know WHY? 👇 console.log(0 == false); console.log("" == false); console.log(null == undefined); 💥 Output: true true true Wait… WHAT? 😳 Why this happens? Because == does type coercion 👉 It converts values before comparing Step by step: ✔ false → 0 ✔ "" → 0 So internally: 0 == 0 // true 👉 Special case: null == undefined → true (but NOT equal to anything else) Now compare with === 👇 console.log(0 === false); console.log("" === false); 💥 Output: false false Because === checks: ✔ Value ✔ Type No conversion. No surprises. Now the WEIRDEST one 🤯 console.log([] == false); 💥 Output: true Why? [] → "" → 0 false → 0 👉 0 == 0 Yes… JavaScript really did that 😅 💡 Takeaway: ✔ == tries to be “smart” (and fails) ✔ === is strict and predictable ✔ Use === by default 👉 "Always use ===" is not a rule… It’s survival advice. 🔁 Save this (you’ll forget this later) 💬 Comment "===" if this clicked ❤️ Like for more JS quirks #javascript #frontend #codingtips #webdevelopment #js #developer

**AVOID JAVASCRIPT'S QUIET BUGS:**   **Don't use ==, use ===** --- 🔺 **THE PROBLEM: == COERCION** ```js console.log([] == false); // prints true! 😅 ``` **The behind-the-scenes journey:** ``` []   ↓ (empty array) ""   ↓ (string) 0   ↓ (number) false   ↓ (boolean) 0 ``` Wait, why is that true?   JavaScript silently converts types, leading to unexpected results. **This is confusing behavior!** --- 🔺 **THE FIX: STRICT EQUALITY** ```js console.log([] === false); // prints false! 🎉 ``` Uses strict comparison without hidden type conversions.   **Predictable and safe.** --- 🔺 **NO HIDDEN CONVERSION!** --- **MAKING YOUR CODE PREDICTABLE: ALWAYS USE ===** Have you encountered confusing JavaScript type coercion? Share your experience! 👇 #javascript #webdevelopment #frontend #coding #developers #mern #learning

🚀 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

🎡 JavaScript Event Loop — Quick Challenge Most developers get this wrong 👀 🧪 What will be the output of this code? (Check the image 👇) 👉 Drop your answer in the comments before scrolling. ⏳ Think first... . . . ✅ Answer 1. Start 4. End 3. Promise.then (Microtask) 2. setTimeout (Macrotask) 🔍 Simple Explanation JavaScript runs code in this order: 1️⃣ First → Normal (synchronous) code 2️⃣ Then → All Promises (Microtasks) 3️⃣ Finally → setTimeout (Macrotasks) 👉 Even if setTimeout is 0, it still runs later. 🧠 Takeaway Promise.then → runs sooner setTimeout → runs later Simple rule, but super useful in real projects. 💬 What was your answer? #JavaScript #EventLoop #Frontend #WebDevelopment #CodingTips

🧠 == vs === in JavaScript (One Small Difference That Causes Big Bugs) One of the first things I learned in JavaScript was: 👉 Always use === instead of == But I didn’t fully understand why until I saw how they actually behave. Here’s a simple breakdown 👇 🔹 == (Loose Equality) == compares values after type conversion (type coercion). Example: 0 == "0" // true false == 0 // true JavaScript tries to convert values to the same type before comparing. This can lead to unexpected results. 🔹 === (Strict Equality) === compares both value and type. Example: 0 === "0" // false false === 0 // false No type conversion happens here. 🔹 Why this matters Using == can introduce subtle bugs because of automatic type coercion. Using === makes your code: ✅ more predictable ✅ easier to debug ✅ less error-prone 💡 One thing I’ve learned: Small JavaScript concepts like this can have a big impact on code reliability. Curious to hear from other developers 👇 Do you ever use ==, or do you always stick with ===? #javascript #frontenddevelopment #webdevelopment #reactjs #softwareengineering #developers