Vijay Shekh’s Post

Most beginners jump straight to frameworks like React. I chose to go back to basics with vanilla JavaScript instead. 🧠 I built a Stories app using HTML, CSS & JavaScript (ES5) — not for show, but to strengthen my core fundamentals. No libraries. No shortcuts. Just logic, structure and pure JavaScript. This project helped me sharpen: • DOM manipulation • Event handling • Managing UI state • Writing cleaner, structured ES5 code • Understanding user interactions Sometimes the fastest way forward is to go back to the roots. Master the fundamentals, and frameworks become easier. 👉 Curious to know: What core concept should every frontend developer master before moving to frameworks? 🔗 Live Demo: https://lnkd.in/gSmm2N_g 📂 GitHub: https://lnkd.in/gRVcS5vq #BuildInPublic #JavaScript #FrontendDeveloper #WebDevelopment #LearningJourney #100DaysOfCode #Coding

🚀 Your Bundle Size Guide Just Got Better – Updated Techniques! 🚀 Dropped the definitive JavaScript bundle optimization guide on javascriptdoctor.blog – now with 2026's latest techniques that actually ship to production. "Optimizing Bundle Size in JavaScript Applications" Proven wins from real apps: ✅ Tree-shaking lodash → 97% smaller (68KB → 2KB) ✅ React.lazy() route splitting (450KB → 120KB initial) ✅ Brotli compression beats Gzip by 76% ✅ Native fetch() kills axios bloat ✅ Vite vs webpack vs esbuild benchmarks Lighthouse scores jumped from red → green. Users actually stay. Read the updated guide: https://lnkd.in/gGZhds8b Quick win: Run npx webpack-bundle-analyzer today. You'll find your lodash/moment culprit immediately. What's YOUR biggest bundle bloat source? Drop it below! 👇 #JavaScript #Performance #NextJS #ReactJS #WebDev

New Blog Published: Understanding global vs globalThis in JavaScript Ever wondered why global works in Node.js but breaks in the browser? Many developers use global variables but don’t fully understand how JavaScript handles them across different environments. In this blog, I break down: • What global really is in Node.js • Why browsers don’t recognize global • How globalThis solves this problem • Key differences with real examples • When to use globalThis in real projects Trick for You all:- 𝗜 𝗵𝗮𝘃𝗲 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 𝗴𝗹𝗼𝗯𝗮𝗹𝗧𝗵𝗶𝘀 𝗮𝘀: 𝗦𝗮𝗯𝗸𝗮 𝗠𝗮𝗹𝗶𝗸 𝗘𝗸 ,haha😝😆! Simple, practical, and straight to the point. 🔗 Read here: https://lnkd.in/gCNvZnqg Grateful to learn from Hitesh Choudhary sir, Piyush Garg sir, Akash Kadlag sir and Chai Aur Code team. #JavaScript #NodeJS #WebDevelopment #Programming #BackendDevelopment #ChaiCode

I built TryJS — a free JavaScript & TypeScript playground that runs entirely in your browser. No backend, no signup. Just open tryjs.app and start coding. A few things under the hood: • TypeScript transpiled in-browser via Sucrase • npm imports resolved through esm.sh — just write import _ from "lodash" and it works • Sandboxed execution with 5s timeout • Export your code as styled PNG screenshots • Share or embed via URL Built with Preact, CodeMirror 6, and Vite. ~6KB gzip for the UI layer. Try it: https://tryjs.app

Many developers jump directly into React hooks, libraries, and frameworks. But the real foundation is much simpler 👇 ✅ Strong JavaScript fundamentals React is just JavaScript at its core. If you truly understand: • Closures • Scope & Hoisting • Async/Await & Promises • Array methods (map, filter, reduce) • ES6 concepts (arrow functions, destructuring, spread) Then React becomes easier, cleaner, and more powerful. Libraries can change. Frameworks can evolve. But strong JavaScript fundamentals stay forever. 💯 Before mastering React… master JavaScript. What’s your opinion? 👇 #ReactJS #JavaScript #FrontendDevelopment #WebDevelopment #CodingJourney

🚀 Built a Todo List App using JavaScript & React! I recently created a Todo List project in two ways — first using pure JavaScript and then rebuilding it using React to understand the difference in handling data and UI. ✨ Features: • Add & Delete Tasks • Tasks saved in Local Storage (data stays after refresh) • Simple and clean UI 💡 What I learned: • DOM Manipulation using JavaScript • useState for state management in React • Handling user input and events • Using Local Storage with JSON.stringify() & JSON.parse() • Difference between Vanilla JS approach vs React approach This project really helped me understand how React makes UI updates easier and more structured compared to JavaScript. Small steps, but moving forward every day in my learning journey 💻✨ #ReactJS #JavaScript #FrontendDevelopment #WebDevelopment #LearningJourney

Every new web developer wants to jump straight into React 🚀 — but real growth happens step by step. Strong foundations in HTML/CSS and JavaScript, combined with version control skills like Git & GitHub, make React (and any framework) much easier to master. There are no shortcuts in tech — only structured learning, consistency, and practice. Build the basics. Trust the process. Level up with confidence. 💻✨ #WebDevelopment #FrontendDeveloper #ReactJS #JavaScript #HTML #CSS #Git #GitHub #CodingJourney #TechCareers #LearnToCode #Developers #Programming #CareerGrowth

Blog Post App (JavaScript Practice Project) Day 9 of my JavaScript learning journey. Built a simple blog post app using HTML, CSS, and Vanilla JavaScript where users can create blog posts with a title, description, and image. Posts are displayed dynamically on the page without using any backend. This project helped me practice real-world DOM manipulation and event handling concepts. ✨ What I learned: Working with querySelector & NodeList Handling events with addEventListener Dynamic UI updates Showing/hiding sections Basic state management in JavaScript 🛠 Tech Stack: HTML CSS JavaScript 🎯 Goal: To improve my JavaScript logic and understand how dynamic content works in real projects. project link: https://lnkd.in/gajJ-s56; github:https://lnkd.in/g8RF2Bbd; #100DaysOfCode #JavaScript #FrontendDevelopment #WebDevelopment #LearningInPublic #MiniProject #DOMManipulation #BuildInPublic #sheriyanscodingschool

Ever wondered how JavaScript actually knows where to return after one function calls another? It's all thanks to the **call stack** — JavaScript's simple but powerful mechanism for tracking function execution. Think of it like a stack of plates in a kitchen: - You add new plates (function calls) on top - You only remove from the top (LIFO: Last In, First Out) - The function on top must finish before anything below can continue Without it, nested calls, recursion, and even basic returns would break. In my latest blog post, I break it down step-by-step: → How the stack grows and shrinks during execution → What an execution context really contains → Why infinite recursion causes "Maximum call stack size exceeded" → How to read stack traces like a pro in DevTools → Why async code (setTimeout, fetch) behaves the way it does If you're working with functions, recursion, or debugging JS errors, this will level up your mental model. What’s one call stack or recursion gotcha that tripped you up early in your JS journey? Drop it below — I'd love to hear! 👇 https://lnkd.in/eQnKbegR #JavaScript #WebDevelopment #Programming #Coding #Tech

JavaScript Practice – Find Even Numbers Today I practiced a simple JavaScript program to find even numbers from an array. Question: Write a function to find even numbers from an array. Code: function evenNumbers(arr){ return arr.filter(function(num){ return num % 2 === 0; }); } console.log(evenNumbers([1,2,3,4,5,6])); Output: [2,4,6] Explanation: • filter() – Creates a new array based on a condition • num % 2 === 0 – Checks if the number is even • Returns only even numbers from the array I am currently learning Frontend Development and practicing JavaScript programs daily. #javascript #frontenddeveloper #codingpractice #webdevelopment #learning