npm installs more than dependencies

Small but useful Node.js tutorial 👇🏼 Improving CLI output with styleText (built-in, no dependencies). Instead of relying on external libraries like chalk, Node.js now provides styleText via node:util for styling terminal output. Step by step: 1️⃣ Add styleText 2️⃣ Apply styles to CLI messages (success, warning, error) 3️⃣ Run the script 4️⃣ Get clean, readable terminal output Important note: CLI colors depend on the terminal and environment. styleText respects NO_COLOR, which makes it more accessible and production-friendly. If you want to understand the motivation behind this change and how to migrate from chalk, check the official Node.js post 👇🏼 🔗 https://lnkd.in/eYdwyCmv A small change, but a nice improvement for scripts, tooling, and internal CLIs. #NodeJS #DeveloperTools #CLI #JavaScript #DX

Day 5 – Node.js Understanding Promises Today’s topic: Promises in Node.js. Promises are used to handle asynchronous operations in a structured way and avoid callback nesting. A Promise has three states: • Pending • Fulfilled (Resolved) • Rejected .then() is used for success handling. .catch() is used for error handling. Promises make asynchronous code more readable and maintainable compared to callbacks. Next: async/await – a cleaner way to write asynchronous code. #NodeJS #BackendDevelopment #JavaScript #AsyncProgramming #SoftwareEngineering

𝐓𝐢𝐫𝐞𝐝 𝐨𝐟 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐢𝐧𝐠 𝐏𝐫𝐞𝐭𝐭𝐢𝐞𝐫 𝐢𝐧 𝐞𝐯𝐞𝐫𝐲 𝐧𝐞𝐰 𝐩𝐫𝐨𝐣𝐞𝐜𝐭? 😬 So I built something for DEVELOPERS. I created a new NPM package that: ✅ Auto-configures Prettier ✅ Sorts imports automatically ✅ Sorts Tailwind classes ✅ Automatically creates prettier.config.js with optimized defaults ✅ Generates a .prettierignore file with commonly ignored paths No manual setup. No copy-pasting config from old repos. No wasting 20 minutes on formatting setup. Just run → done. 💯 It works across: - HTML / CSS - JavaScript - TypeScript - React - Next.js And more… The goal was simple: Remove friction. Increase consistency. Ship faster. Would love your feedback. Sharing a quick demo and npm link in the comments: 👇🏻

𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗴𝗿𝗲𝗮𝘁, 𝗯𝘂𝘁 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗮 𝗴𝗮𝗺𝗲-𝗰𝗵𝗮𝗻𝗴𝗲𝗿. 🚀 One of the biggest headaches in plain JS is passing the wrong type of argument to a function and only finding out at runtime. TypeScript solves this by letting us define strict contracts for our code. By simply adding types to your parameters and explicitly stating your return type, you get two massive benefits: 1️⃣ Instant IDE autocomplete 2️⃣ Catching bugs before you even hit save // The TypeScript Way 🛡️ function calculateDiscount(price: number, discount: number = 10): number {   return price - (price * (discount / 100)); } // Hovering over this, your IDE knows exactly what to expect! const finalPrice = calculateDiscount(500); Once you start strictly typing your functions, you never want to go back. I’ve just uploaded a new video diving deep into everything you need to know about functions in TypeScript. It’s the latest episode in my ongoing TypeScript series on YouTube, where we're breaking down these concepts step by step. 𝗖𝗵𝗲𝗰𝗸 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗳𝘂𝗹𝗹 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗵𝗲𝗿𝗲: https://lnkd.in/gyexUVgs What’s your favourite TS feature that saves you the most time during debugging? Let me know in the comments! #TypeScript #JavaScript #WebDevelopment #SoftwareEngineering #CodingTutorial #DeveloperCommunity

Yarn vs npm — quick breakdown Both Yarn and npm are package managers for Node.js, but they differ in how they handle dependencies at scale. #Yarn Faster installs via parallel dependency fetching Strict and deterministic installs using yarn.lock Better consistency across development, CI, and production #npm Bundled with Node.js Mature ecosystem and wide adoption Improved performance in recent versions Key point: For team-based and production-grade projects, dependency determinism matters — this is where Yarn often has an edge. #NodeJS #Yarn #NPM #BackendEngineering #JavaScript #LearningJourney

TypeScript doesn't make your code better. It just makes bad code fail faster. After migrating 3 projects from JavaScript to TypeScript, here's my controversial take: ❌ TypeScript won't fix: - Poor architecture - Bad API design - Terrible variable names - Lack of testing - Spaghetti code ✅ TypeScript helps with: - Catching runtime errors at compile time - Self-documenting code (types as docs) - Better IDE autocomplete - Refactoring confidence - Team collaboration The Trap vs. The Reality 👇 Check the image below for the code comparison My rule: - Ban 'any' type (use 'unknown' instead) - Define interfaces for everything - Use strict mode ALWAYS - Type your environment variables TypeScript is a tool, not a solution. Write good code, then add types. Not the other way around. Agree or nah? 👇 #TypeScript #JavaScript #CodeQuality #HotTake

Node.js is single-threaded... but still handles thousands of requests. How? Understanding how Node.js really works helped me write more efficient, non-blocking backend code. Here’s a high-level breakdown of what powers Node behind the scenes: V8 compiles your JavaScript to machine code Node bindings handle OS-level tasks (like file & network) libuv manages the Event Loop and async operations Worker threads pick up blocking tasks in the background The result? A fast, non-blocking system that can scale even with a single thread. I used to treat Node.js like a black box. But once I understood this flow, debugging async code got a lot easier. Have you explored how the Node.js event loop works behind the scenes? #NodeJS #BackendDevelopment #JavaScript #WebPerformance #AsyncProgramming

Want to reuse code without rewriting the same logic again and again? That’s where inheritance in JavaScript classes becomes powerful. By extending a parent class, the child class automatically gets access to its properties and methods, making your code cleaner, structured, and scalable. This concept is heavily used in real-world applications to maintain modular architecture and reduce redundancy. Mastering OOP in JavaScript strengthens your foundation for React, Node, and full-stack development. Follow for more JavaScript concepts and practical coding projects. #JavaScript #WebDevelopment #ES6 #FullStackDeveloper

Starting React? Then remember these 2 JSX rules 👇 ✅ JSX must return only one parent element React components can’t return multiple siblings directly. Wrap them inside a div or React Fragment. ✅ Use className, not class Because JSX is JavaScript, and class is a reserved keyword. Small rules. Big difference when learning React. 💬 Which mistake did you make first — multiple elements or class vs className? Comment 1 or 2 👇 📌 Save this for React basics 👥 Follow for simple frontend learning