<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>eslint — FixDevs</title><description>Latest fixes and solutions for eslint errors on FixDevs.</description><link>https://fixdevs.com/</link><language>en</language><lastBuildDate>Thu, 26 Mar 2026 00:00:00 GMT</lastBuildDate><atom:link href="https://fixdevs.com/tags/eslint/rss.xml" rel="self" type="application/rss+xml"/><item><title>Fix: ESLint Config Not Working — Rules Ignored, Flat Config Errors, or Plugin Not Found</title><link>https://fixdevs.com/blog/eslint-config-not-working/</link><guid isPermaLink="true">https://fixdevs.com/blog/eslint-config-not-working/</guid><description>How to fix ESLint configuration issues — flat config vs legacy config, extends conflicts, parser options, plugin resolution, per-directory overrides, and migrating to ESLint 9.</description><pubDate>Thu, 26 Mar 2026 00:00:00 GMT</pubDate><category>eslint</category><category>javascript</category><category>typescript</category><category>frontend</category><category>debugging</category><author>FixDevs</author></item><item><title>Fix: ESLint no-unused-vars False Positives and Configuration</title><link>https://fixdevs.com/blog/eslint-no-unused-vars-false-positive/</link><guid isPermaLink="true">https://fixdevs.com/blog/eslint-no-unused-vars-false-positive/</guid><description>How to fix ESLint no-unused-vars false positives — TypeScript types, destructuring ignores, React imports, function arguments, and configuring the rule to match your codebase patterns.</description><pubDate>Thu, 19 Mar 2026 00:00:00 GMT</pubDate><category>eslint</category><category>javascript</category><category>typescript</category><category>debugging</category><category>frontend</category><author>FixDevs</author></item><item><title>Fix: ESLint import/no-unresolved Error (Module Exists but ESLint Can&apos;t Find It)</title><link>https://fixdevs.com/blog/eslint-import-no-unresolved/</link><guid isPermaLink="true">https://fixdevs.com/blog/eslint-import-no-unresolved/</guid><description>How to fix ESLint&apos;s import/no-unresolved errors when modules actually resolve correctly — configure eslint-import-resolver-typescript, fix path alias settings, and handle node_modules that ESLint cannot find.</description><pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate><category>eslint</category><category>typescript</category><category>javascript</category><category>debugging</category><category>tooling</category><author>FixDevs</author></item><item><title>Fix: VSCode ESLint Extension Not Working – No Errors Shown or Not Running</title><link>https://fixdevs.com/blog/vscode-eslint-not-working/</link><guid isPermaLink="true">https://fixdevs.com/blog/vscode-eslint-not-working/</guid><description>How to fix VSCode&apos;s ESLint extension when it stops highlighting errors, shows no output, or fails to start. Covers flat config, settings, and common misconfigurations.</description><pubDate>Mon, 02 Feb 2026 00:00:00 GMT</pubDate><category>vscode</category><category>eslint</category><category>javascript</category><author>FixDevs</author></item><item><title>Fix: ESLint Parsing error: Unexpected token (JSX, TypeScript, ES modules)</title><link>https://fixdevs.com/blog/eslint-parsing-error-unexpected-token/</link><guid isPermaLink="true">https://fixdevs.com/blog/eslint-parsing-error-unexpected-token/</guid><description>How to fix ESLint &apos;Parsing error: Unexpected token&apos; for JSX, TypeScript, and ES module syntax by configuring the correct parser, parserOptions, and ESLint config format.</description><pubDate>Wed, 21 Jan 2026 00:00:00 GMT</pubDate><category>eslint</category><category>javascript</category><category>typescript</category><author>FixDevs</author></item></channel></rss>