Code Quality Beyond Linting with SonarQube and Code Climate

🚀 Day 78 – Linting & Code Formatting (ESLint + Prettier Setup) Today I focused on improving code quality and consistency by setting up linting and formatting tools in my Node.js project. Clean code is just as important as working code! 💻✨ 🔹 What I Learned Today ✔ ESLint Helps identify potential errors, bad practices, and unused code in JavaScript. ✔ Prettier Automatically formats code to maintain a consistent style across the project. ✔ Integration Configured ESLint and Prettier together to avoid formatting conflicts and keep the codebase clean. 🔹 Why It Matters • Improves code readability • Maintains consistent formatting across teams • Helps catch bugs early • Makes collaboration easier in real projects Small improvements like this make a big difference in writing professional and maintainable code 🚀 #100DaysOfCode #NodeJS #JavaScript #ESLint #Prettier #CodeQuality #BackendDevelopment #DeveloperJourney

A lot of new developers miss an important point: Async code isn’t just about following rules. It actually requires a different way of thinking. When I first started using Node.js, I realized my biggest challenge wasn’t actually JavaScript itself. What really got me stuck was the confusing flow of control. With synchronous code, it’s easy to see the path from start to finish. But in async systems, things work differently: • The order in which things run isn’t always predictable • Errors might show up in places you don’t expect • The state of your program can change between steps • Debugging doesn’t always follow a straight line Over time, you stop just writing code and start thinking about how your whole system works as it runs. That’s when things started to make sense for me. But I still spend a lot of time dealing with async patterns. I’m curious, when did async programming finally make sense for you? And what do you advise me to overcome “the fear” of async systems?

Most developers know var is bad… Yet it’s still showing up in codebases in 2026 😬 Here’s why it keeps breaking things 👇 🔴 var is function-scoped, hoisted, and re-declarable → Leads to silent, hard-to-trace bugs 🟢 const is block-scoped and strict → Fails fast, catches mistakes early, keeps your code predictable 💡 The rule is simple: → const by default — always → let when reassignment is needed → var — never again ⚡ Quick 5-second fix: Add "no-var": "error" to your ESLint config and enforce it across your team 👀 Still seeing var in your codebase? Drop a 😅 — you’re definitely not alone ♻️ Repost this to save your team hours of debugging 👉 Follow Mohd Sharfuddin Khan for daily JavaScript tips that actually level up your coding #JavaScript #WebDevelopment #Frontend #CodingTips #CleanCode #Developers #ESLint #JSDaily #WebDevelopment #FrontendDeveloper #100DaysOfCode #CodeTips #LearnToCode #ProgrammingTips #TechCommunity #DevLife

Here's an unpopular take that'll probably get me blocked by half the frontend community: TypeScript was JavaScript's biggest mistake. I've been building systems for 15 years. Seen teams at enterprise scale struggle with this. Here's what actually happens: • Developers spend 40% more time on type definitions than business logic • Complex generics for simple object operations • Config hell: tsconfig, eslint, webpack interdependencies • Junior developers get stuck on type gymnastics instead of learning programming fundamentals • Runtime bugs still happen because types disappear JavaScript's flexibility was a feature, not a bug. Dynamic typing lets you prototype fast, iterate quickly, and solve problems creatively. TypeScript promised safety but delivered complexity. We added a compile step to a runtime language and convinced ourselves it was progress. Don't get me wrong - types have their place. But JavaScript with good testing, clear naming, and proper validation catches the same bugs with less overhead. Sometimes the simple solution is the right solution. #viral #trending #trend #typescript #javascript #webdev #programming #developer #coding #frontend #backend #softwareengineering #tech #unpopularopinion #hotteake #development #programminglife #techopinions

A typical React + TypeScript project linting setup looks something like this: - eslint - @typescript-eslint/parser - @typescript-eslint/eslint-plugin - eslint-plugin-react - eslint-plugin-react-hooks - prettier - eslint-config-prettier That is 7 packages before you have written a single line of application code. And that is before you start fighting the config to make ESLint and Prettier not conflict with each other. I have set up this exact combination more times than I would like to admit. Every time it works, but it never feels like it should be this complicated. I recently came across Biome (https://biomejs.dev/). It is a linter and formatter in one tool, written in Rust. Here is what caught my attention: - TypeScript support is built in, no extra packages needed - Linting and formatting in one tool, one config file, no conflicts - Can lint only staged files with --staged flag built in, no need for additional tools - Reported to be significantly faster than ESLint and Prettier combined - Already supports a large portion of common ESLint rules out of the box The entire setup is one package: @biomejs/biome I am planning to use it on my next project. The reduction in setup complexity alone makes it worth trying. Have you already migrated to Biome? I would love to hear about your experiences, especially any gotchas to watch out for.

Why We Migrated 6,000+ TypeScript Files from ESLint to oxlint Sharing my work and thoughts on the code quality in the age of AI assist coding as well as Rust based JS toolings. My first contribution to the oxc project. https://lnkd.in/eccazNqF #rust #jstooling #javascript #typescript #reactjs #oxlint #voidzero

I ran into a nasty problem during a recent PR. 👉 133 files changed 👉 Merge conflicts everywhere 👉 ESLint took forever just to clean up imports At that point, I stopped relying on ESLint for this specific task and built something focused instead. So I created a VS Code extension that: ⚡ Removes unused + duplicate imports ⚡ Runs instantly on save (zero config) ⚡ Works with JavaScript, TypeScript, and React It’s not meant to replace ESLint — just to handle one job fast, especially in large or messy codebases. If you’ve ever dealt with slow fixes during big PRs, this might actually help. Would love honest feedback — where does it break? 👇 Extension URL for VSCODE: https://lnkd.in/dmitmEBd

We're back with another update on react-infinite-scroll-component(https://lnkd.in/gZgRuSkG)! 🥁 When I took over as maintainer, I laid out a 4-phase roadmap to bring this library back to life. Today, we're crossing off Phase 2 with the release of v7.0.0. 🎉 Here's where we stand: ✅ Phase 1 — Comprehensive test suites & CI/CD automation (v6.1.1) ✅ Phase 2 — React 17 migration (v7.0.0) 🔜 Phase 3 — TypeScript conversion & modern React features 🔜 Phase 4 — Accessibility improvements & enhanced documentation What shipped in v7: - React 17 peer dependency support - Jest + React Testing Library test coverage - Storybook upgraded from v5 to v7 - Revamped CI/CD with automated publish workflows - ESLint, Prettier, and Husky configured for contributor-friendly DX - Node.js 18+ baseline 109k+ dependents. Still going. Still breaking nothing. Huge thanks to Ankeet Maini for the trust, and to everyone who's filed issues, opened PRs, or just starred the repo, your patience means a lot. I'll be actively going through open issues and PRs now, so if you've been waiting, your turn is coming. 🙌🏻 #OpenSource #React #JavaScript #TypeScript #WebDevelopment #Community #Maintainership

I've taken hundreds of typing tests. Every single one used "the quick brown fox jumps over the lazy dog." Cool sentence. Completely useless for developers. You know what's actually hard to type fast? webpack, esLint, TypeScript, useCallback, package.json So we built a typing test with real developer words. Three modes: — Code snippets — Dev vocabulary — Famous programmer quotes It's free. No signup. No paywall. If you're a developer who actually wants to improve your typing speed on the stuff you TYPE EVERY DAY, go try it: https://lnkd.in/grTuV77S What's your WPM on dev words? Drop it below. 👇 (I'll start: 74 WPM, 96% accuracy. Webpack almost broke me.)

Yesterday, I took a complex React Native feature from an empty screen to a fully tested, high-fidelity port in a single afternoon. The secret wasn't coding faster. It was 45 minutes of aggressive "Scope-Locking" before I wrote a single line of code. My rules for rapid iteration: Lock the Scope: Define exact non-functional requirements upfront (e.g., visual parity only, mock data, no backend integration yet). Shift Left on Quality: Linting (Biome) and Testing (RNTL) aren't "cleanup" tasks. They are gates. Zero code gets committed until all 57 tests are green. Treating engineering as infrastructure management, where rules prevent debt from ever entering the codebase, is how you maintain momentum without burning out.