eslint 9.22.0 → 9.24.0

package/README.md

@@ -20,9 +20,9 @@
 
 ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:
 
-* ESLint uses [Espree](https://github.com/eslint/js/tree/main/packages/espree) for JavaScript parsing.
-* ESLint uses an AST to evaluate patterns in code.
-* ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.
+-   ESLint uses [Espree](https://github.com/eslint/js/tree/main/packages/espree) for JavaScript parsing.
+-   ESLint uses an AST to evaluate patterns in code.
+-   ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.
 
 ## Table of Contents
 
@@ -75,21 +75,21 @@ You can configure rules in your `eslint.config.js` files as in this example:
 import { defineConfig } from "eslint/config";
 
 export default defineConfig([
-    {
-        files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
-        rules: {
-            "prefer-const": "warn",
-            "no-constant-binary-expression": "error"
-        }
-    }
+	{
+		files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
+		rules: {
+			"prefer-const": "warn",
+			"no-constant-binary-expression": "error",
+		},
+	},
 ]);
 ```
 
 The names `"prefer-const"` and `"no-constant-binary-expression"` are the names of [rules](https://eslint.org/docs/rules) in ESLint. The first value is the error level of the rule and can be one of these values:
 
-* `"off"` or `0` - turn the rule off
-* `"warn"` or `1` - turn the rule on as a warning (doesn't affect exit code)
-* `"error"` or `2` - turn the rule on as an error (exit code will be 1)
+-   `"off"` or `0` - turn the rule off
+-   `"warn"` or `1` - turn the rule on as a warning (doesn't affect exit code)
+-   `"error"` or `2` - turn the rule on as an error (exit code will be 1)
 
 The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the [configuration docs](https://eslint.org/docs/latest/use/configure)).
 
@@ -109,16 +109,16 @@ ESLint adheres to the [OpenJS Foundation Code of Conduct](https://eslint.org/con
 
 Before filing an issue, please be sure to read the guidelines for what you're reporting:
 
-* [Bug Report](https://eslint.org/docs/latest/contribute/report-bugs)
-* [Propose a New Rule](https://eslint.org/docs/latest/contribute/propose-new-rule)
-* [Proposing a Rule Change](https://eslint.org/docs/latest/contribute/propose-rule-change)
-* [Request a Change](https://eslint.org/docs/latest/contribute/request-change)
+-   [Bug Report](https://eslint.org/docs/latest/contribute/report-bugs)
+-   [Propose a New Rule](https://eslint.org/docs/latest/contribute/propose-new-rule)
+-   [Proposing a Rule Change](https://eslint.org/docs/latest/contribute/propose-rule-change)
+-   [Request a Change](https://eslint.org/docs/latest/contribute/request-change)
 
 ## Frequently Asked Questions
 
 ### Does ESLint support JSX?
 
-Yes, ESLint natively supports parsing JSX syntax (this must be enabled in [configuration](https://eslint.org/docs/latest/use/configure)). Please note that supporting JSX syntax *is not* the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn't recognize. We recommend using [eslint-plugin-react](https://www.npmjs.com/package/eslint-plugin-react) if you are using React and want React semantics.
+Yes, ESLint natively supports parsing JSX syntax (this must be enabled in [configuration](https://eslint.org/docs/latest/use/configure)). Please note that supporting JSX syntax _is not_ the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn't recognize. We recommend using [eslint-plugin-react](https://www.npmjs.com/package/eslint-plugin-react) if you are using React and want React semantics.
 
 ### Does Prettier replace ESLint?
 
@@ -174,32 +174,32 @@ ESLint takes security seriously. We work hard to ensure that ESLint is safe for
 
 ESLint follows [semantic versioning](https://semver.org). However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:
 
-* Patch release (intended to not break your lint build)
-    * A bug fix in a rule that results in ESLint reporting fewer linting errors.
-    * A bug fix to the CLI or core (including formatters).
-    * Improvements to documentation.
-    * Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
-    * Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
-* Minor release (might break your lint build)
-    * A bug fix in a rule that results in ESLint reporting more linting errors.
-    * A new rule is created.
-    * A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
-    * A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
-    * An existing rule is deprecated.
-    * A new CLI capability is created.
-    * New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
-    * A new formatter is created.
-    * `eslint:recommended` is updated and will result in strictly fewer linting errors (e.g., rule removals).
-* Major release (likely to break your lint build)
-    * `eslint:recommended` is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
-    * A new option to an existing rule that results in ESLint reporting more linting errors by default.
-    * An existing formatter is removed.
-    * Part of the public API is removed or changed in an incompatible way. The public API includes:
-        * Rule schemas
-        * Configuration schema
-        * Command-line options
-        * Node.js API
-        * Rule, formatter, parser, plugin APIs
+-   Patch release (intended to not break your lint build)
+    -   A bug fix in a rule that results in ESLint reporting fewer linting errors.
+    -   A bug fix to the CLI or core (including formatters).
+    -   Improvements to documentation.
+    -   Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
+    -   Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
+-   Minor release (might break your lint build)
+    -   A bug fix in a rule that results in ESLint reporting more linting errors.
+    -   A new rule is created.
+    -   A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
+    -   A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
+    -   An existing rule is deprecated.
+    -   A new CLI capability is created.
+    -   New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
+    -   A new formatter is created.
+    -   `eslint:recommended` is updated and will result in strictly fewer linting errors (e.g., rule removals).
+-   Major release (likely to break your lint build)
+    -   `eslint:recommended` is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
+    -   A new option to an existing rule that results in ESLint reporting more linting errors by default.
+    -   An existing formatter is removed.
+    -   Part of the public API is removed or changed in an incompatible way. The public API includes:
+        -   Rule schemas
+        -   Configuration schema
+        -   Command-line options
+        -   Node.js API
+        -   Rule, formatter, parser, plugin APIs
 
 According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (`~`) in `package.json` e.g. `"eslint": "~3.1.0"` to guarantee the results of your builds.
 
@@ -313,6 +313,7 @@ Percy Ma
 
 <!-- NOTE: This section is autogenerated. Do not manually edit.-->
 <!--sponsorsstart-->
+
 ## Sponsors
 
 The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. [Become a Sponsor](https://eslint.org/donate)
@@ -320,12 +321,13 @@ to get your logo on our READMEs and [website](https://eslint.org/sponsors).
 
 <h3>Platinum Sponsors</h3>
 <p><a href="https://automattic.com"><img src="https://images.opencollective.com/automattic/d0ef3e1/logo.png" alt="Automattic" height="128"></a> <a href="https://www.airbnb.com/"><img src="https://images.opencollective.com/airbnb/d327d66/logo.png" alt="Airbnb" height="128"></a></p><h3>Gold Sponsors</h3>
-<p><a href="https://qlty.sh/"><img src="https://images.opencollective.com/qltysh/33d157d/logo.png" alt="Qlty Software" height="96"></a> <a href="https://trunk.io/"><img src="https://images.opencollective.com/trunkio/fb92d60/avatar.png" alt="trunk.io" height="96"></a> <a href="https://shopify.engineering/"><img src="https://avatars.githubusercontent.com/u/8085" alt="Shopify" height="96"></a></p><h3>Silver Sponsors</h3>
-<p><a href="https://vite.dev/"><img src="https://images.opencollective.com/vite/e6d15e1/logo.png" alt="Vite" height="64"></a> <a href="https://www.jetbrains.com/"><img src="https://images.opencollective.com/jetbrains/fe76f99/logo.png" alt="JetBrains" height="64"></a> <a href="https://liftoff.io/"><img src="https://images.opencollective.com/liftoff/5c4fa84/logo.png" alt="Liftoff" height="64"></a> <a href="https://stackblitz.com"><img src="https://avatars.githubusercontent.com/u/28635252" alt="StackBlitz" height="64"></a></p><h3>Bronze Sponsors</h3>
+<p><a href="https://qlty.sh/"><img src="https://images.opencollective.com/qltysh/33d157d/logo.png" alt="Qlty Software" height="96"></a> <a href="https://trunk.io/"><img src="https://images.opencollective.com/trunkio/fb92d60/avatar.png" alt="trunk.io" height="96"></a></p><h3>Silver Sponsors</h3>
+<p><a href="https://vite.dev/"><img src="https://images.opencollective.com/vite/e6d15e1/logo.png" alt="Vite" height="64"></a> <a href="https://liftoff.io/"><img src="https://images.opencollective.com/liftoff/5c4fa84/logo.png" alt="Liftoff" height="64"></a> <a href="https://stackblitz.com"><img src="https://avatars.githubusercontent.com/u/28635252" alt="StackBlitz" height="64"></a></p><h3>Bronze Sponsors</h3>
 <p><a href="https://cybozu.co.jp/"><img src="https://images.opencollective.com/cybozu/933e46d/logo.png" alt="Cybozu" height="32"></a> <a href="https://www.crosswordsolver.org/anagram-solver/"><img src="https://images.opencollective.com/anagram-solver/2666271/logo.png" alt="Anagram Solver" height="32"></a> <a href="https://icons8.com/"><img src="https://images.opencollective.com/icons8/7fa1641/logo.png" alt="Icons8" height="32"></a> <a href="https://discord.com"><img src="https://images.opencollective.com/discordapp/f9645d9/logo.png" alt="Discord" height="32"></a> <a href="https://www.gitbook.com"><img src="https://avatars.githubusercontent.com/u/7111340" alt="GitBook" height="32"></a> <a href="https://nolebase.ayaka.io"><img src="https://avatars.githubusercontent.com/u/11081491" alt="Neko" height="32"></a> <a href="https://nx.dev"><img src="https://avatars.githubusercontent.com/u/23692104" alt="Nx" height="32"></a> <a href="https://opensource.mercedes-benz.com/"><img src="https://avatars.githubusercontent.com/u/34240465" alt="Mercedes-Benz Group" height="32"></a> <a href="https://herocoders.com"><img src="https://avatars.githubusercontent.com/u/37549774" alt="HeroCoders" height="32"></a> <a href="https://www.lambdatest.com"><img src="https://avatars.githubusercontent.com/u/171592363" alt="LambdaTest" height="32"></a></p>
 <h3>Technology Sponsors</h3>
 Technology sponsors allow us to use their products and services for free as part of a contribution to the open source ecosystem and our work.
 <p><a href="https://netlify.com"><img src="https://raw.githubusercontent.com/eslint/eslint.org/main/src/assets/images/techsponsors/netlify-icon.svg" alt="Netlify" height="32"></a> <a href="https://algolia.com"><img src="https://raw.githubusercontent.com/eslint/eslint.org/main/src/assets/images/techsponsors/algolia-icon.svg" alt="Algolia" height="32"></a> <a href="https://1password.com"><img src="https://raw.githubusercontent.com/eslint/eslint.org/main/src/assets/images/techsponsors/1password-icon.svg" alt="1Password" height="32"></a></p>
+
 <!--sponsorsend-->
 
 [tidelift]: https://tidelift.com/funding/github/npm/eslint

package/bin/eslint.js

@@ -16,7 +16,7 @@ mod.enableCompileCache?.();
 
 // must do this initialization *before* other requires in order to work
 if (process.argv.includes("--debug")) {
-    require("debug").enable("eslint:*,-eslint:code-path,eslintrc:*");
+	require("debug").enable("eslint:*,-eslint:code-path,eslintrc:*");
 }
 
 //------------------------------------------------------------------------------
@@ -45,20 +45,20 @@ if (process.argv.includes("--debug")) {
  * @returns {Promise<string>} The read text.
  */
 function readStdin() {
-    return new Promise((resolve, reject) => {
-        let content = "";
-        let chunk = "";
-
-        process.stdin
-            .setEncoding("utf8")
-            .on("readable", () => {
-                while ((chunk = process.stdin.read()) !== null) {
-                    content += chunk;
-                }
-            })
-            .on("end", () => resolve(content))
-            .on("error", reject);
-    });
+	return new Promise((resolve, reject) => {
+		let content = "";
+		let chunk = "";
+
+		process.stdin
+			.setEncoding("utf8")
+			.on("readable", () => {
+				while ((chunk = process.stdin.read()) !== null) {
+					content += chunk;
+				}
+			})
+			.on("end", () => resolve(content))
+			.on("error", reject);
+	});
 }
 
 /**
@@ -67,34 +67,32 @@ function readStdin() {
  * @returns {string} The error message.
  */
 function getErrorMessage(error) {
-
-    // Lazy loading because this is used only if an error happened.
-    const util = require("node:util");
-
-    // Foolproof -- third-party module might throw non-object.
-    if (typeof error !== "object" || error === null) {
-        return String(error);
-    }
-
-    // Use templates if `error.messageTemplate` is present.
-    if (typeof error.messageTemplate === "string") {
-        try {
-            const template = require(`../messages/${error.messageTemplate}.js`);
-
-            return template(error.messageData || {});
-        } catch {
-
-            // Ignore template error then fallback to use `error.stack`.
-        }
-    }
-
-    // Use the stacktrace if it's an error object.
-    if (typeof error.stack === "string") {
-        return error.stack;
-    }
-
-    // Otherwise, dump the object.
-    return util.format("%o", error);
+	// Lazy loading because this is used only if an error happened.
+	const util = require("node:util");
+
+	// Foolproof -- third-party module might throw non-object.
+	if (typeof error !== "object" || error === null) {
+		return String(error);
+	}
+
+	// Use templates if `error.messageTemplate` is present.
+	if (typeof error.messageTemplate === "string") {
+		try {
+			const template = require(`../messages/${error.messageTemplate}.js`);
+
+			return template(error.messageData || {});
+		} catch {
+			// Ignore template error then fallback to use `error.stack`.
+		}
+	}
+
+	// Use the stacktrace if it's an error object.
+	if (typeof error.stack === "string") {
+		return error.stack;
+	}
+
+	// Otherwise, dump the object.
+	return util.format("%o", error);
 }
 
 /**
@@ -116,21 +114,21 @@ let hadFatalError = false;
  * @returns {void}
  */
 function onFatalError(error) {
-    process.exitCode = 2;
-    hadFatalError = true;
+	process.exitCode = 2;
+	hadFatalError = true;
 
-    const { version } = require("../package.json");
-    const message = `
+	const { version } = require("../package.json");
+	const message = `
 Oops! Something went wrong! :(
 
 ESLint: ${version}
 
 ${getErrorMessage(error)}`;
 
-    if (!displayedErrors.has(message)) {
-        console.error(message);
-        displayedErrors.add(message);
-    }
+	if (!displayedErrors.has(message)) {
+		console.error(message);
+		displayedErrors.add(message);
+	}
 }
 
 //------------------------------------------------------------------------------
@@ -138,42 +136,46 @@ ${getErrorMessage(error)}`;
 //------------------------------------------------------------------------------
 
 (async function main() {
-    process.on("uncaughtException", onFatalError);
-    process.on("unhandledRejection", onFatalError);
-
-    // Call the config initializer if `--init` is present.
-    if (process.argv.includes("--init")) {
-
-        // `eslint --init` has been moved to `@eslint/create-config`
-        console.warn("You can also run this command directly using 'npm init @eslint/config@latest'.");
-
-        const spawn = require("cross-spawn");
-
-        spawn.sync("npm", ["init", "@eslint/config@latest"], { encoding: "utf8", stdio: "inherit" });
-        return;
-    }
-
-    // Otherwise, call the CLI.
-    const cli = require("../lib/cli");
-    const exitCode = await cli.execute(
-        process.argv,
-        process.argv.includes("--stdin") ? await readStdin() : null,
-        true
-    );
-
-    /*
-     * If an uncaught exception or unhandled rejection was detected in the meantime,
-     * keep the fatal exit code 2 that is already assigned to `process.exitCode`.
-     * Without this condition, exit code 2 (unsuccessful execution) could be overwritten with
-     * 1 (successful execution, lint problems found) or even 0 (successful execution, no lint problems found).
-     * This ensures that unexpected errors that seemingly don't affect the success
-     * of the execution will still cause a non-zero exit code, as it's a common
-     * practice and the default behavior of Node.js to exit with non-zero
-     * in case of an uncaught exception or unhandled rejection.
-     *
-     * Otherwise, assign the exit code returned from CLI.
-     */
-    if (!hadFatalError) {
-        process.exitCode = exitCode;
-    }
-}()).catch(onFatalError);
+	process.on("uncaughtException", onFatalError);
+	process.on("unhandledRejection", onFatalError);
+
+	// Call the config initializer if `--init` is present.
+	if (process.argv.includes("--init")) {
+		// `eslint --init` has been moved to `@eslint/create-config`
+		console.warn(
+			"You can also run this command directly using 'npm init @eslint/config@latest'.",
+		);
+
+		const spawn = require("cross-spawn");
+
+		spawn.sync("npm", ["init", "@eslint/config@latest"], {
+			encoding: "utf8",
+			stdio: "inherit",
+		});
+		return;
+	}
+
+	// Otherwise, call the CLI.
+	const cli = require("../lib/cli");
+	const exitCode = await cli.execute(
+		process.argv,
+		process.argv.includes("--stdin") ? await readStdin() : null,
+		true,
+	);
+
+	/*
+	 * If an uncaught exception or unhandled rejection was detected in the meantime,
+	 * keep the fatal exit code 2 that is already assigned to `process.exitCode`.
+	 * Without this condition, exit code 2 (unsuccessful execution) could be overwritten with
+	 * 1 (successful execution, lint problems found) or even 0 (successful execution, no lint problems found).
+	 * This ensures that unexpected errors that seemingly don't affect the success
+	 * of the execution will still cause a non-zero exit code, as it's a common
+	 * practice and the default behavior of Node.js to exit with non-zero
+	 * in case of an uncaught exception or unhandled rejection.
+	 *
+	 * Otherwise, assign the exit code returned from CLI.
+	 */
+	if (!hadFatalError) {
+		process.exitCode = exitCode;
+	}
+})().catch(onFatalError);

package/conf/default-cli-options.js

@@ -6,27 +6,27 @@
 "use strict";
 
 module.exports = {
-    configFile: null,
-    baseConfig: false,
-    rulePaths: [],
-    useEslintrc: true,
-    envs: [],
-    globals: [],
-    extensions: null,
-    ignore: true,
-    ignorePath: void 0,
-    cache: false,
+	configFile: null,
+	baseConfig: false,
+	rulePaths: [],
+	useEslintrc: true,
+	envs: [],
+	globals: [],
+	extensions: null,
+	ignore: true,
+	ignorePath: void 0,
+	cache: false,
 
-    /*
-     * in order to honor the cacheFile option if specified
-     * this option should not have a default value otherwise
-     * it will always be used
-     */
-    cacheLocation: "",
-    cacheFile: ".eslintcache",
-    cacheStrategy: "metadata",
-    fix: false,
-    allowInlineConfig: true,
-    reportUnusedDisableDirectives: void 0,
-    globInputPaths: true
+	/*
+	 * in order to honor the cacheFile option if specified
+	 * this option should not have a default value otherwise
+	 * it will always be used
+	 */
+	cacheLocation: "",
+	cacheFile: ".eslintcache",
+	cacheStrategy: "metadata",
+	fix: false,
+	allowInlineConfig: true,
+	reportUnusedDisableDirectives: void 0,
+	globInputPaths: true,
 };

package/conf/ecma-version.js

@@ -12,5 +12,5 @@
 const LATEST_ECMA_VERSION = 2025;
 
 module.exports = {
-    LATEST_ECMA_VERSION
+	LATEST_ECMA_VERSION,
 };