ar
Feedback

لا تقع ضحية للمخادعين! تيليمتريو يكتشف ويُميّز هذه القنوات 👉 إذا كنت تريد رؤية العلامة، اشترك

React (Native & JS) | Redux | JS | Typescript

React (Native & JS) | Redux | JS | Typescript

الذهاب إلى القناة على Telegram

Best place to have good collections of resources. Be a part of this channel and improve your React knowledge.😍❣️

إظهار المزيد
4 441
المشتركون
-124 ساعات
-47 أيام
-2030 أيام
أرشيف المشاركات
🚀 React Native 0.88 — What’s new? 👀 Don’t miss what’s changing in React Native! 👇 Check out the latest post and swipe through. 🔗 https://www.instagram.com/p/Den2K7Bk7tA/?rpxt=d2J0OWJsbDNzNGM5

🚨 HTTP Status Codes — the ones every developer should know 401 vs 403 301 vs 302 vs 307 502 vs 503 vs 504 👀 Do you actually
🚨 HTTP Status Codes — the ones every developer should know 401 vs 403 301 vs 302 vs 307 502 vs 503 vs 504 👀 Do you actually know the difference? We put together a complete 1xx → 5xx HTTP Status Code cheat sheet — including the codes that matter for interviews and real-world debugging. 📌 Save this one. You’ll need it later. 👇 Check out the full carousel on Instagram: https://www.instagram.com/p/Ddd7KboEwVx/?stkn=MTN3bnU3eWcya2c3MQ== Follow @codemane.dev for more practical software engineering content.

🚨 Next.js devs, this warning looks scary: “Hydration failed because the server rendered HTML didn’t match the client.” 😵‍💫
🚨 Next.js devs, this warning looks scary: “Hydration failed because the server rendered HTML didn’t match the client.” 😵‍💫 But do you know how to actually read the warning and find the mismatch? 👀 We broke it down in the new CodeMane carousel — including the common mistakes and the useEffect() trap. 👇 Check it out on Instagram: https://www.instagram.com/p/DdatyT4k9or/?stkn=bHZwcm5kNThzd2U3 💾 Save it. Your next hydration error might thank you.

🚨 React 19 quietly changed two APIs you’ve probably used for years. forwardRef() → ref as a prop .Provider → Less boilerplat
🚨 React 19 quietly changed two APIs you’ve probably used for years. forwardRef() → ref as a prop .Provider → <Context> Less boilerplate. Cleaner React. 👀 Want to see exactly what changed? 👉 Check the full carousel on Instagram: https://www.instagram.com/p/DdMJAP1k7yj/?stkn=cHp3bTk2N3RsZnpw Save it. You’ll probably need this one later. 💾

👀 You know useEffect… But have you heard about useEffectEvent? React 19.2 just made Effects a little more interesting. 👀 Th
👀 You know useEffect… But have you heard about useEffectEvent? React 19.2 just made Effects a little more interesting. 👀 There’s a reason this new Hook exists — and it solves a problem many React devs have probably faced. 👇 See the carousel to understand it 👉 https://www.instagram.com/p/DdEupLtk-ja/?stkn=MXA0ZmZndXM1YjE0 - @codemane.dev

🚀 How does React keep your UI responsive when there’s a LOT of work to do? React doesn’t make JavaScript multithreaded. 👀 I
🚀 How does React keep your UI responsive when there’s a LOT of work to do? React doesn’t make JavaScript multithreaded. 👀 Instead, it can break rendering work, prioritize updates, and yield to the browser. That’s where Concurrent Rendering & Time Slicing come in. I’ve broken it down visually in the latest CodeMane carousel 👇 👉 Read the full post: https://www.instagram.com/p/Dc8aum4DjKZ/?stkn=MmYzYzRtbmEzYzF5 💾 Save it if you’re learning React or preparing for frontend interviews. Code Less. Engineer More.

🚨 You were told let & const aren’t hoisted. But… that’s not exactly true. 👀 TDZ + Shadowing = a nasty JavaScript interview
🚨 You were told let & const aren’t hoisted. But… that’s not exactly true. 👀 TDZ + Shadowing = a nasty JavaScript interview trap. 😈 Can you guess the output before seeing the answer? 👇 Check the carousel: https://www.instagram.com/p/Dc1GctDk6CC/?igsi=Z3FidWVrdGcyaG1z @codemane.dev

🚨 Your CI pipeline can be green… while your API key is already leaked. Ever wondered how secrets accidentally make their way
🚨 Your CI pipeline can be green… while your API key is already leaked. Ever wondered how secrets accidentally make their way from your .env → Git → CI/CD → production? This carousel breaks down the leaked API key story and the safer way to handle secrets in CI/CD. 🔐 👉 Check out the full post on Instagram: View the CodeMane carousel on Instagram 💾 Save it. You’ll want this before your next deployment. — CodeMane 🚀

🚨 Your bundle size doubled… but you only added ONE import. Could a simple export * be the reason? 👀 We just broke down how
🚨 Your bundle size doubled… but you only added ONE import. Could a simple export * be the reason? 👀 We just broke down how barrel files can silently expand your dependency graph — and what you can check when your bundle suddenly gets bigger. 👉 See the full breakdown on Instagram: https://www.instagram.com/p/DcnuidbDrrs/?igsi=MWg0eHkwMnJzd2xjMg== 📌 Save it. You might need this the next time your bundle size looks suspicious.

🚀 How does YouTube stream 4K without buffering every few seconds? It’s not magic. 👀 Chunks + Adaptive Bitrate + Buffering +
🚀 How does YouTube stream 4K without buffering every few seconds? It’s not magic. 👀 Chunks + Adaptive Bitrate + Buffering + CDNs work together behind the scenes. Want to see how the whole pipeline works? 👇 📲 Check out the full carousel on Instagram: https://www.instagram.com/p/DclSdn7kwxC/?igsi=dXlpdmZvYTRoYm5k Save it for your next System Design interview. 🧠 — CodeMane 💻

🚀 React Compiler Deconstructed: What Happened to useMemo? React Compiler is changing how we think about React performance op
🚀 React Compiler Deconstructed: What Happened to useMemo? React Compiler is changing how we think about React performance optimization. But does that mean useMemo is dead? 👀 Not quite. In this carousel, we break down: ⚡ Why we used useMemo in the first place 🧠 How React Compiler can optimize code automatically 🔄 Manual vs compiler-assisted memoization ❌ Why you shouldn’t blindly remove useMemo 📈 What developers should actually do The key mental shift: Manual optimization → Compiler-assisted optimization And remember: Don’t blindly add useMemo. Don’t blindly remove it either. Measure what actually matters. 📌 Save the carousel for your next React performance review. 📲 Read the full carousel on Instagram: CodeMane on Instagram — React Compiler & useMemo 👉 Follow @codemane.dev for practical React, JavaScript & frontend engineering content.

🔍 The 3 Pillars of Observability Your production app is slow… but WHY? 🤔 This carousel breaks down the three pillars that h
🔍 The 3 Pillars of Observability Your production app is slow… but WHY? 🤔 This carousel breaks down the three pillars that help you understand what’s happening inside your system: 📝 Logs → What happened? 📊 Metrics → How much / how often? 🔗 Traces → Where did it happen? And the real power comes when you use all three together to find the root cause. 👇 Check out the full carousel on Instagram: 👇👇👇👇 View the CodeMane Instagram post 👆👆👆👆 💾 Save it for your next production debugging session. 👨‍💻 Follow @codemane.dev for more developer concepts explained simply.

New post!! Most developers get the execution order of ⁠process.nextTick⁠, ⁠Promise⁠, and ⁠app.listen⁠ wrong. Can you solve th
New post!! Most developers get the execution order of ⁠process.nextTick⁠, ⁠Promise⁠, and ⁠app.listen⁠ wrong. Can you solve this? 👇 Check the code & solve it here: https://www.instagram.com/reel/DcToPzhsKCw/?igsi=MXhjbjZkejBsdzAzcw== 💡 Detailed step-by-step breakdown is inside the reel description. 👉 Follow @codemane.dev for more daily JavaScript & backend concepts!

🧠 Can You Guess the JavaScript Output? What will this print? 👀 console.log([] + []); Think you know the answer? 🤔 Check ou
🧠 Can You Guess the JavaScript Output? What will this print? 👀 console.log([] + []); Think you know the answer? 🤔 Check out the Reel for the answer + explanation 👇 https://www.instagram.com/reel/DcQiQL4TU5G/?igsh=M3JqY3QzZzYzNmJm 🔥 Follow @codemane.dev for more JavaScript challenges, frontend tricks & developer concepts. #JavaScript #CodingChallenge #CodeMane

🚀 New CodeMane Post: What Actually Happens Inside React? 🤯 We use React every day, but what is actually happening behind th
🚀 New CodeMane Post: What Actually Happens Inside React? 🤯 We use React every day, but what is actually happening behind the scenes when React renders your UI? This carousel breaks down React Fiber in a simple visual way: ⚛️ Why React needed Fiber 🧩 What a Fiber actually is 🌳 How the Fiber Tree works 🔄 Current vs Work-in-Progress trees ⚡ How React manages rendering work 🔍 Fiber vs Reconciliation 🚀 Render Phase vs Commit Phase 🌐 When the DOM actually gets updated The key mental model: Fiber ≠ DOM Fiber ≠ Reconciliation Render ≠ Commit Once this clicks, React’s rendering process becomes much easier to understand. 🧠 📌 Save this post for when you dive into React internals. 📸 Read the full carousel on Instagram: https://www.instagram.com/p/DcOfYpekwTW/?igsh=MXMyZjFqYmg5cmIybw== Follow @codemane.dev for more practical React & frontend concepts 💙 #ReactJS #ReactFiber #FrontendDevelopment

🚀 New CodeMane Post: React Reconciliation Finally Makes Sense 🤯 Ever wondered what actually happens when React re-renders?
🚀 New CodeMane Post: React Reconciliation Finally Makes Sense 🤯 Ever wondered what actually happens when React re-renders? React doesn’t simply rebuild the entire DOM every time something changes. In this carousel, we break down: 🧠 How React compares previous & new renders ⚙️ What reconciliation actually does 🔄 Same type vs different type 🔑 Why React needs key 😬 Why index keys can cause unexpected behavior 🧩 How keys affect component identity 🚀 Render → Reconcile → Commit mental model The biggest takeaway: React doesn’t rebuild everything. It figures out what changed — and preserves what it can. Swipe through all 10 slides and get the complete mental model 👇 📌 Save it for your next React debugging session! 📸 Instagram: https://www.instagram.com/p/DcNlgL6Dp03/?igsh=MWc1bnVlaG9pOXZkbA== Follow @codemane.dev for more practical frontend & React content 💙 #ReactJS #FrontendDevelopment #JavaScript

🚨 Do you REALLY understand package.json? You probably see it in almost every JavaScript/TypeScript project… React ⚛️ React N
🚨 Do you REALLY understand package.json? You probably see it in almost every JavaScript/TypeScript project… React ⚛️ React Native 📱 Next.js Vite Node.js and more. But package.json has a lot more going on than just dependencies. In this carousel, we go from the basics to some concepts many developers overlook: 🔹 dependencies vs devDependencies vs peerDependencies 🔹 ^ vs ~ vs exact versions 🔹 package.json → lock file → node_modules 🔹 npm install vs npm ci 🔹 npm lifecycle scripts & postinstall 🔹 type, engines, exports & overrides 🔹 Workspaces & monorepos 🧠 One mental model to remember: package.json → What your project allows lock file → What was resolved node_modules → What was installed 📌 Save this one — you’ll want it later. 👉 Read the full carousel on Instagram: https://www.instagram.com/p/DcJWdpVjBZ-/?igsh=bzV1eGNkcGZtYnM3 💬 Which package.json concept did you learn something new about? — CodeMane.dev Code Less. Engineer More. 🚀

🚀 New CodeMane Post is LIVE! 🔐 Web Security + TypeScript JWT, Cookies, HttpOnly &amp; Partial — do you know how they actual
🚀 New CodeMane Post is LIVE! 🔐 Web Security + TypeScript JWT, Cookies, HttpOnly & Partial<T> — do you know how they actually differ? In this carousel, we break down: 🔑 JWT → Token format 🍪 Cookies → Browser-managed storage/transport 🛡️ HttpOnly → Helps prevent JavaScript from reading cookies 🧩 Partial → Makes TypeScript properties optional Also covered: ❌ Common authentication mistakes 🔐 Secure cookie flags ⚠️ XSS considerations 🚀 Practical TypeScript usage 📌 Save it. Share it. Keep it handy for your next auth implementation. 👉 Read the full carousel on Instagram: https://www.instagram.com/p/Db-H-UHE6G5/?igsh=MXE5cGk3M3ptd3AyMg== 💬 Which topic should CodeMane explain with a real-world example next? Follow CodeMane.dev for more real-world software engineering tips. ⚡

🚀 Node.js Fundamentals You Should Actually Understand Node.js isn’t just about writing JavaScript on the server. This new Co
🚀 Node.js Fundamentals You Should Actually Understand Node.js isn’t just about writing JavaScript on the server. This new CodeMane carousel breaks down 3 important concepts: 🔹 Streams — Process data in chunks instead of loading everything into memory. 🔹 Modules — Structure your application using reusable pieces of code. 🔹 CommonJS vs ESM — Understand require() vs import and module.exports vs export. 💡 These concepts become especially important when you’re working with real-world Node.js applications. 📌 Save this one for your next Node.js project. 👉 Read the full carousel on Instagram: https://www.instagram.com/p/Db5-lWDE5OY/?igsh=MTRtYnY2eDBkNXQyOA== 💬 What Node.js concept should CodeMane explain next? — Follow CodeMane.dev for more useful contents. Code Less. Engineer More. ⚡