0 views collected around this technical thread.
The article reviews Biome's rapid progress in 2024—including multiple minor releases, new commands, expanded language support, team growth, awards, and IDE integrations—while outlining the ambitious 2025 roadmap featuring plugins, domain‑based linting, monorepo enhancements, multi‑file analysis, type inference, and broader language support.
This article traces the evolution of ESLint from its early role as a simple JavaScript linter to the introduction of the Flat Config system in ESLint 9, examines the challenges of extends, multi‑format support, plugins, and shared configurations, and explores new tools like Config Inspector, eslint‑flat‑config‑utils, ESLint Stylistic, and future multi‑language support.
This article explains the new features and breaking changes of ESLint v9, demonstrates how to use the @antfu/eslint-config preset with flat configuration, and shows how to set up Husky Git hooks to enforce linting and automatic fixing in JavaScript projects.
The cpp-linter-action tool, a GitHub Action for C/C++ linting, has been updated to version 2.9.0 adding a Pull Request Review feature that posts suggestions directly in PRs, along with other functionalities such as Annotations, Thread Comments, and Step Summaries.
The article traces ESLint’s evolution from a JSLint‑style checker to the dominant JavaScript linter, explains its long‑standing clash with the opinionated formatter Prettier over code‑style rules, and details the team’s decision in v8.53.0 to deprecate built‑in formatting rules in favor of external style plugins and market‑driven style guides.
This article explains the fundamentals of ESLint, including its purpose, configuration files, AST-based analysis, the SourceCode abstraction, rule template creation, key functions, and the overall linting and fixing workflow, enabling developers to build custom linting plugins for consistent code style.
This tutorial demonstrates how to set up a Python project, install and run Pylint, interpret its messages, and improve code quality by adding docstrings, fixing formatting issues, and configuring suppression, while also covering linting on single files, directories, and common pitfalls.
This article introduces a set of ESLint rules that help developers write safer and more efficient asynchronous JavaScript by avoiding common pitfalls such as async promise executors, awaiting in loops, improper promise handling, and callback-related race conditions.
The article explains how to design and implement ESLint and StyleLint plugins for the San‑Native framework, detailing AST generation, processor creation, rule definitions for JavaScript and CSS, configuration sharing, and how these tools provide real‑time linting feedback for developers.
The article explains how using functions that were not intended as callbacks—such as library utilities, Web APIs, or option objects—can break when array.map or other higher‑order functions pass extra arguments, and it shows safer patterns, TypeScript behavior, and linting hints to prevent these bugs.
This article explains how GrowingIO's Design System leverages a component library and introduces essential frontend development tools—including Prettier, stylelint, ESLint, Commitizen, commitlint, lint‑staged, and Husky—detailing their installation, configuration, usage, and integration into CI pipelines to ensure consistent, maintainable code.
This guide traces ESLint’s evolution from early lint tools, shows how to install and configure it, run auto‑fixes, integrate with editors, enforce quality via Husky, lint‑staged and commit‑lint, and combine these practices into a defensive moat that keeps repositories clean and consistent.
An experienced Python engineer shares three indispensable tools—Kite for AI‑powered code completion, Mypy for static type checking, and SonarLint for real‑time linting—explaining their benefits, usage examples, and how they improve coding speed, reliability, and error detection.