<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Eslint on Commentary of Takao</title><link>https://takao.blog/en/tags/eslint/</link><description>Recent content in Eslint on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/eslint/index.xml" rel="self" type="application/rss+xml"/><item><title>ESLint Flat Config: Migration Guide from Legacy .eslintrc</title><link>https://takao.blog/en/web/eslint-flat-config/</link><pubDate>Mon, 26 Feb 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/eslint-flat-config/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post ESLint Flat Config: Migration Guide from Legacy .eslintrc" /&gt;&lt;p&gt;ESLint v9.0, released in 2024, made the flat config system (&lt;code&gt;eslint.config.js&lt;/code&gt;) the default, replacing the legacy &lt;code&gt;.eslintrc&lt;/code&gt; format that had been in use for over a decade. This migration guide covers the complete transition process, new concepts, and practical examples.&lt;/p&gt;
&lt;h2 id="why-flat-config"&gt;Why Flat Config?
&lt;/h2&gt;&lt;p&gt;The legacy &lt;code&gt;.eslintrc&lt;/code&gt; system had several problems: configuration cascading made behavior unpredictable, directory-based resolution was complex, JSON/YAML lacked support for functions and comments, and shareable configs were difficult to compose. Flat config addresses these with a single configuration file, explicit composition via JavaScript arrays, simplified plugin resolution, and full JavaScript-native syntax.&lt;/p&gt;</description></item></channel></rss>