[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-2910":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":18,"compositeScore":19,"rankGlobal":9,"rankLanguage":9,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":21,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":15,"starSnapshotCount":15,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},2910,"eslint","eslint\u002Feslint","Find and fix problems in your JavaScript code.","https:\u002F\u002Feslint.org",null,"JavaScript",27307,5021,326,84,0,45,111,9,100,"MIT License",false,"main",[24,5,25,26,27],"ecmascript","javascript","linter","static-code-analysis","2026-06-12 04:00:16","[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Feslint.svg)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Feslint)\n[![Downloads](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002Feslint.svg)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Feslint)\n[![Build Status](https:\u002F\u002Fgithub.com\u002Feslint\u002Feslint\u002Fworkflows\u002FCI\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Feslint\u002Feslint\u002Factions)\n\u003Cbr>\n[![Open Collective Backers](https:\u002F\u002Fimg.shields.io\u002Fopencollective\u002Fbackers\u002Feslint)](https:\u002F\u002Fopencollective.com\u002Feslint)\n[![Open Collective Sponsors](https:\u002F\u002Fimg.shields.io\u002Fopencollective\u002Fsponsors\u002Feslint)](https:\u002F\u002Fopencollective.com\u002Feslint)\n\n# ESLint\n\n[Website](https:\u002F\u002Feslint.org) |\n[Configure ESLint](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fuse\u002Fconfigure) |\n[Rules](https:\u002F\u002Feslint.org\u002Fdocs\u002Frules\u002F) |\n[Contribute to ESLint](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute) |\n[Report Bugs](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute\u002Freport-bugs) |\n[Code of Conduct](https:\u002F\u002Feslint.org\u002Fconduct) |\n[X](https:\u002F\u002Fx.com\u002Fgeteslint) |\n[Discord](https:\u002F\u002Feslint.org\u002Fchat) |\n[Mastodon](https:\u002F\u002Ffosstodon.org\u002F@eslint) |\n[Bluesky](https:\u002F\u002Fbsky.app\u002Fprofile\u002Feslint.org)\n\nESLint is a tool for identifying and reporting on patterns found in ECMAScript\u002FJavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:\n\n- ESLint uses [Espree](https:\u002F\u002Fgithub.com\u002Feslint\u002Fjs\u002Ftree\u002Fmain\u002Fpackages\u002Fespree) for JavaScript parsing.\n- ESLint uses an AST to evaluate patterns in code.\n- ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.\n\n## Table of Contents\n\n1. [Installation and Usage](#installation-and-usage)\n1. [Configuration](#configuration)\n1. [Version Support](#version-support)\n1. [Code of Conduct](#code-of-conduct)\n1. [Filing Issues](#filing-issues)\n1. [Frequently Asked Questions](#frequently-asked-questions)\n1. [Releases](#releases)\n1. [Security Policy](#security-policy)\n1. [Semantic Versioning Policy](#semantic-versioning-policy)\n1. [ESM Dependencies](#esm-dependencies)\n1. [License](#license)\n1. [Team](#team)\n1. [Sponsors](#sponsors)\n1. [Technology Sponsors](#technology-sponsors) \u003C!-- markdownlint-disable-line MD051 -->\n\n## Installation and Usage\n\n### Prerequisites\n\nTo use ESLint, you must have [Node.js](https:\u002F\u002Fnodejs.org\u002F) (`^20.19.0`, `^22.13.0`, or `>=24`) installed and built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)\n\nIf you use ESLint's TypeScript type definitions, TypeScript 5.3 or later is required.\n\n### npm Installation\n\nYou can install and configure ESLint using this command:\n\n```shell\nnpm init @eslint\u002Fconfig@latest\n```\n\nAfter that, you can run ESLint on any file or directory like this:\n\n```shell\nnpx eslint yourfile.js\n```\n\n### pnpm Installation\n\nTo use ESLint with pnpm, we recommend setting up a `.npmrc` file with at least the following settings:\n\n```text\nauto-install-peers=true\nnode-linker=hoisted\n```\n\nThis ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.\n\n## Configuration\n\nYou can configure rules in your `eslint.config.js` files as in this example:\n\n```js\nimport { defineConfig } from \"eslint\u002Fconfig\";\n\nexport default defineConfig([\n\t{\n\t\tfiles: [\"**\u002F*.js\", \"**\u002F*.cjs\", \"**\u002F*.mjs\"],\n\t\trules: {\n\t\t\t\"prefer-const\": \"warn\",\n\t\t\t\"no-constant-binary-expression\": \"error\",\n\t\t},\n\t},\n]);\n```\n\nThe names `\"prefer-const\"` and `\"no-constant-binary-expression\"` are the names of [rules](https:\u002F\u002Feslint.org\u002Fdocs\u002Frules) in ESLint. The first value is the error level of the rule and can be one of these values:\n\n- `\"off\"` or `0` - turn the rule off\n- `\"warn\"` or `1` - turn the rule on as a warning (doesn't affect exit code)\n- `\"error\"` or `2` - turn the rule on as an error (exit code will be 1)\n\nThe three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the [configuration docs](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fuse\u002Fconfigure)).\n\n## Version Support\n\nThe ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.\n\nESLint offers commercial support for both current and previous versions through our partners, [Tidelift][tidelift] and [HeroDevs][herodevs].\n\nSee [Version Support](https:\u002F\u002Feslint.org\u002Fversion-support) for more details.\n\n## Code of Conduct\n\nESLint adheres to the [OpenJS Foundation Code of Conduct](https:\u002F\u002Feslint.org\u002Fconduct).\n\n## Filing Issues\n\nBefore filing an issue, please be sure to read the guidelines for what you're reporting:\n\n- [Bug Report](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute\u002Freport-bugs)\n- [Propose a New Rule](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute\u002Fpropose-new-rule)\n- [Proposing a Rule Change](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute\u002Fpropose-rule-change)\n- [Request a Change](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute\u002Frequest-change)\n\n## Frequently Asked Questions\n\n### Does ESLint support JSX?\n\nYes, ESLint natively supports parsing JSX syntax (this must be enabled in [configuration](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fuse\u002Fconfigure)). 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:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Feslint-plugin-react) if you are using React and want React semantics.\n\n### Does Prettier replace ESLint?\n\nNo, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to [Prettier's documentation](https:\u002F\u002Fprettier.io\u002Fdocs\u002Fen\u002Finstall#eslint-and-other-linters) to learn how to configure them to work well with each other.\n\n### What ECMAScript versions does ESLint support?\n\nESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through [configuration](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fuse\u002Fconfigure).\n\n### What about experimental features?\n\nESLint's parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.\n\nIn other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and\u002For rule plugins. If you are using Babel, you can use [@babel\u002Feslint-parser](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@babel\u002Feslint-parser) and [@babel\u002Feslint-plugin](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@babel\u002Feslint-plugin) to use any option available in Babel.\n\nOnce a language feature has been adopted into the ECMAScript standard (stage 4 according to the [TC39 process](https:\u002F\u002Ftc39.github.io\u002Fprocess-document\u002F)), we will accept issues and pull requests related to the new feature, subject to our [contributing guidelines](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fcontribute). Until then, please use the appropriate parser and plugin(s) for your experimental feature.\n\n### Which Node.js versions does ESLint support?\n\nESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint's supported Node.js versions are updated to be:\n\n1. The most recent maintenance release of Node.js\n1. The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.\n1. The Node.js Current release\n\nESLint is also expected to work with Node.js versions released after the Node.js Current release.\n\nRefer to the [Quick Start Guide](https:\u002F\u002Feslint.org\u002Fdocs\u002Flatest\u002Fuse\u002Fgetting-started#prerequisites) for the officially supported Node.js versions for a given ESLint release.\n\n### Where to ask for help?\n\nOpen a [discussion](https:\u002F\u002Fgithub.com\u002Feslint\u002Feslint\u002Fdiscussions) or stop by our [Discord server](https:\u002F\u002Feslint.org\u002Fchat).\n\n### Why doesn't ESLint lock dependency versions?\n\nLock files like `package-lock.json` are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.\n\nPackages like `eslint` that get published to the npm registry do not include lock files. `npm install eslint` as a user will respect version constraints in ESLint's `package.json`. ESLint and its dependencies will be included in the user's lock file if one exists, but ESLint's own lock file would not be used.\n\nWe intentionally don't lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.\n\nThe Twilio blog has a [deeper dive](https:\u002F\u002Fwww.twilio.com\u002Fblog\u002Flockfiles-nodejs) to learn more.\n\n## Releases\n\nWe have scheduled releases every two weeks on Friday or Saturday. You can follow a [release issue](https:\u002F\u002Fgithub.com\u002Feslint\u002Feslint\u002Fissues?q=is%3Aopen+is%3Aissue+label%3Arelease) for updates about the scheduling of any particular release.\n\n## Security Policy\n\nESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full [security policy](https:\u002F\u002Fgithub.com\u002Feslint\u002F.github\u002Fblob\u002Fmaster\u002FSECURITY.md).\n\n## Semantic Versioning Policy\n\nESLint follows [semantic versioning](https:\u002F\u002Fsemver.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:\n\n- Patch release (intended to not break your lint build)\n    - A bug fix in a rule that results in ESLint reporting fewer linting errors.\n    - A bug fix to the CLI or core (including formatters).\n    - Improvements to documentation.\n    - Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.\n    - Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).\n- Minor release (might break your lint build)\n    - A bug fix in a rule that results in ESLint reporting more linting errors.\n    - A new rule is created.\n    - A new option to an existing rule that does not result in ESLint reporting more linting errors by default.\n    - 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.\n    - An existing rule is deprecated.\n    - A new CLI capability is created.\n    - New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).\n    - A new formatter is created.\n    - `eslint:recommended` is updated and will result in strictly fewer linting errors (e.g., rule removals).\n- Major release (likely to break your lint build)\n    - `eslint:recommended` is updated and may result in new linting errors (e.g., rule additions, most rule option updates).\n    - A new option to an existing rule that results in ESLint reporting more linting errors by default.\n    - An existing formatter is removed.\n    - Part of the public API is removed or changed in an incompatible way. The public API includes:\n        - Rule schemas\n        - Configuration schema\n        - Command-line options\n        - Node.js API\n        - Rule, formatter, parser, plugin APIs\n\nAccording 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.\n\n## ESM Dependencies\n\nSince ESLint is a CommonJS package, there are restrictions on which ESM-only packages can be used as dependencies.\n\nPackages that are controlled by the ESLint team and have no external dependencies can be safely loaded synchronously using [`require(esm)`](https:\u002F\u002Fnodejs.org\u002Fapi\u002Fmodules.html#loading-ecmascript-modules-using-require) and therefore used in any contexts.\n\nFor external packages, we don't use `require(esm)` because a package could add a top-level `await` and thus break ESLint. We can use an external ESM-only package only in case it is needed only in asynchronous code, in which case it can be loaded using dynamic `import()`.\n\nThese policies don't apply to packages intended for our own usage only, such as `eslint-config-eslint`.\n\n## License\n\nMIT License\n\nCopyright OpenJS Foundation and other contributors, \u003Cwww.openjsf.org>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and\u002For sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n\n## Team\n\nThese folks keep the project moving and are resources for help.\n\n\u003C!-- NOTE: This section is autogenerated. Do not manually edit.-->\n\n\u003C!--teamstart-->\n\n### Technical Steering Committee (TSC)\n\nThe people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.\n\n\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnzakas\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fnzakas.png?s=75\" width=\"75\" height=\"75\" alt=\"Nicholas C. Zakas's Avatar\">\u003Cbr \u002F>\nNicholas C. Zakas\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffasttime\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Ffasttime.png?s=75\" width=\"75\" height=\"75\" alt=\"Francesco Trotta's Avatar\">\u003Cbr \u002F>\nFrancesco Trotta\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmdjermanovic\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fmdjermanovic.png?s=75\" width=\"75\" height=\"75\" alt=\"Milos Djermanovic's Avatar\">\u003Cbr \u002F>\nMilos Djermanovic\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\n\n### Reviewers\n\nThe people who review and implement new features.\n\n\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Faladdin-add\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Faladdin-add.png?s=75\" width=\"75\" height=\"75\" alt=\"唯然's Avatar\">\u003Cbr \u002F>\n唯然\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsnitin315\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fsnitin315.png?s=75\" width=\"75\" height=\"75\" alt=\"Nitin Kumar's Avatar\">\u003Cbr \u002F>\nNitin Kumar\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\n\n### Committers\n\nThe people who review and fix bugs and help triage issues.\n\n\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FDMartens\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FDMartens.png?s=75\" width=\"75\" height=\"75\" alt=\"fnx's Avatar\">\u003Cbr \u002F>\nfnx\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FJoshuaKGoldberg\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FJoshuaKGoldberg.png?s=75\" width=\"75\" height=\"75\" alt=\"Josh Goldberg ✨'s Avatar\">\u003Cbr \u002F>\nJosh Goldberg ✨\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FSwetaTanwar\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FSwetaTanwar.png?s=75\" width=\"75\" height=\"75\" alt=\"Sweta Tanwar's Avatar\">\u003Cbr \u002F>\nSweta Tanwar\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FTanujkanti4441\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FTanujkanti4441.png?s=75\" width=\"75\" height=\"75\" alt=\"Tanuj Kanti's Avatar\">\u003Cbr \u002F>\nTanuj Kanti\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flumirlumir\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Flumirlumir.png?s=75\" width=\"75\" height=\"75\" alt=\"루밀LuMir's Avatar\">\u003Cbr \u002F>\n루밀LuMir\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPixel998\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FPixel998.png?s=75\" width=\"75\" height=\"75\" alt=\"Pixel998's Avatar\">\u003Cbr \u002F>\nPixel998\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\n\n### Website Team\n\nTeam members who focus specifically on eslint.org\n\n\u003Ctable>\u003Ctbody>\u003Ctr>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Famareshsm\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Famareshsm.png?s=75\" width=\"75\" height=\"75\" alt=\"Amaresh  S M's Avatar\">\u003Cbr \u002F>\nAmaresh  S M\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fharish-sethuraman\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fharish-sethuraman.png?s=75\" width=\"75\" height=\"75\" alt=\"Harish's Avatar\">\u003Cbr \u002F>\nHarish\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003Ctd align=\"center\" valign=\"top\" width=\"11%\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkecrily\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fkecrily.png?s=75\" width=\"75\" height=\"75\" alt=\"Percy Ma's Avatar\">\u003Cbr \u002F>\nPercy Ma\n\u003C\u002Fa>\n\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\n\n\u003C!--teamend-->\n\n\u003C!-- NOTE: This section is autogenerated. Do not manually edit.-->\n\u003C!--sponsorsstart-->\n\n## Sponsors\n\nThe following companies, organizations, and individuals support ESLint's ongoing maintenance and development. [Become a Sponsor](https:\u002F\u002Feslint.org\u002Fdonate)\nto get your logo on our READMEs and [website](https:\u002F\u002Feslint.org\u002Fsponsors).\n\n\u003Ch3>Platinum Sponsors\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fautomattic.com\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fautomattic\u002Fd0ef3e1\u002Flogo.png\" alt=\"Automattic\" height=\"128\">\u003C\u002Fa>\u003C\u002Fp>\u003Ch3>Gold Sponsors\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fqlty.sh\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fqltysh\u002F33d157d\u002Flogo.png\" alt=\"Qlty Software\" height=\"96\">\u003C\u002Fa>\u003C\u002Fp>\u003Ch3>Silver Sponsors\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fvite.dev\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fvite\u002Fd472863\u002Flogo.png\" alt=\"Vite\" height=\"64\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fliftoff.io\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fliftoff\u002F2d6c3b6\u002Flogo.png\" alt=\"Liftoff\" height=\"64\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fstackblitz.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28635252\" alt=\"StackBlitz\" height=\"64\">\u003C\u002Fa>\u003C\u002Fp>\u003Ch3>Bronze Sponsors\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fcybozu.co.jp\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fcybozu\u002F933e46d\u002Flogo.png\" alt=\"Cybozu\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fopensource.sap.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2531208\" alt=\"SAP\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fwww.crawljobs.com\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fcrawljobs-poland\u002Ffa43a17\u002Flogo.png\" alt=\"CrawlJobs\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fdepot.dev\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fdepot\u002F39125a1\u002Flogo.png\" alt=\"Depot\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Ficons8.com\u002F\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Ficons8\u002F7fa1641\u002Flogo.png\" alt=\"Icons8\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fdiscord.com\">\u003Cimg src=\"https:\u002F\u002Fimages.opencollective.com\u002Fdiscordapp\u002Ff9645d9\u002Flogo.png\" alt=\"Discord\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fwww.gitbook.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7111340\" alt=\"GitBook\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fherocoders.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37549774\" alt=\"HeroCoders\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fcitadel.co.jp\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75781367\" alt=\"Citadel AI\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fwww.lambdatest.com\">\u003Cimg src=\"https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171592363\" alt=\"TestMu AI Open Source Office (Formerly LambdaTest)\" height=\"32\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Technology Sponsors\u003C\u002Fh3>\nTechnology sponsors allow us to use their products and services for free as part of a contribution to the open source ecosystem and our work.\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fnetlify.com\">\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Feslint\u002Feslint.org\u002Fmain\u002Fsrc\u002Fassets\u002Fimages\u002Ftechsponsors\u002Fnetlify-icon.svg\" alt=\"Netlify\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Falgolia.com\">\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Feslint\u002Feslint.org\u002Fmain\u002Fsrc\u002Fassets\u002Fimages\u002Ftechsponsors\u002Falgolia-icon.svg\" alt=\"Algolia\" height=\"32\">\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002F1password.com\">\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Feslint\u002Feslint.org\u002Fmain\u002Fsrc\u002Fassets\u002Fimages\u002Ftechsponsors\u002F1password-icon.svg\" alt=\"1Password\" height=\"32\">\u003C\u002Fa>\u003C\u002Fp>\n\n\u003C!--sponsorsend-->\n\n[tidelift]: https:\u002F\u002Ftidelift.com\u002Ffunding\u002Fgithub\u002Fnpm\u002Feslint\n[herodevs]: https:\u002F\u002Fwww.herodevs.com\u002Fsupport\u002Feslint-nes?utm_source=ESLintWebsite&utm_medium=ESLintWebsite&utm_campaign=ESLintNES&utm_id=ESLintNES\n","ESLint 是一个用于发现和修复 JavaScript 代码中问题的工具。它基于 Espree 解析器构建，利用抽象语法树（AST）来评估代码模式，并且完全可插拔，允许用户在运行时添加自定义规则。这种灵活性使得 ESLint 成为了开发过程中不可或缺的一部分，适用于需要保证代码质量、遵循编码规范的各种场景，比如团队协作开发、开源项目维护等。此外，其强大的配置能力也支持针对不同项目需求调整检查规则。",2,"2026-06-11 02:51:37","top_language"]