{ "manifest": { "name": "eslint", "version": "8.57.1", "author": { "name": "Nicholas C. Zakas", "email": "nicholas+npm@nczconsulting.com" }, "description": "An AST-based pattern checker for JavaScript.", "bin": { "eslint": "bin/eslint.js" }, "main": "./lib/api.js", "exports": { "./package.json": "./package.json", ".": "./lib/api.js", "./use-at-your-own-risk": "./lib/unsupported-api.js" }, "scripts": { "build:docs:update-links": "node tools/fetch-docs-links.js", "build:site": "node Makefile.js gensite", "build:webpack": "node Makefile.js webpack", "build:readme": "node tools/update-readme.js", "lint": "node Makefile.js lint", "lint:docs:js": "node Makefile.js lintDocsJS", "lint:docs:rule-examples": "node Makefile.js checkRuleExamples", "lint:fix": "node Makefile.js lint -- fix", "lint:fix:docs:js": "node Makefile.js lintDocsJS -- fix", "release:generate:alpha": "node Makefile.js generatePrerelease -- alpha", "release:generate:beta": "node Makefile.js generatePrerelease -- beta", "release:generate:latest": "node Makefile.js generateRelease -- latest", "release:generate:maintenance": "node Makefile.js generateRelease -- maintenance", "release:generate:rc": "node Makefile.js generatePrerelease -- rc", "release:publish": "node Makefile.js publishRelease", "test": "node Makefile.js test", "test:cli": "mocha", "test:fuzz": "node Makefile.js fuzz", "test:performance": "node Makefile.js perf" }, "gitHooks": { "pre-commit": "lint-staged" }, "lint-staged": { "*.js": "eslint --fix", "*.md": "markdownlint --fix", "lib/rules/*.js": [ "node tools/update-eslint-all.js", "git add packages/js/src/configs/eslint-all.js" ], "docs/src/rules/*.md": [ "node tools/check-rule-examples.js", "node tools/fetch-docs-links.js", "git add docs/src/_data/further_reading_links.json" ], "docs/**/*.svg": "npx svgo -r --multipass" }, "files": [ "LICENSE", "README.md", "bin", "conf", "lib", "messages" ], "repository": { "type": "git", "url": "https://github.com/eslint/eslint.git" }, "funding": "https://opencollective.com/eslint", "homepage": "https://eslint.org/", "bugs": { "url": "https://github.com/eslint/eslint/issues/" }, "dependencies": { "@eslint-community/eslint-utils": "^4.2.0", "@eslint-community/regexpp": "^4.6.1", "@eslint/eslintrc": "^2.1.4", "@eslint/js": "8.57.1", "@humanwhocodes/config-array": "^0.13.0", "@humanwhocodes/module-importer": "^1.0.1", "@nodelib/fs.walk": "^1.2.8", "@ungap/structured-clone": "^1.2.0", "ajv": "^6.12.4", "chalk": "^4.0.0", "cross-spawn": "^7.0.2", "debug": "^4.3.2", "doctrine": "^3.0.0", "escape-string-regexp": "^4.0.0", "eslint-scope": "^7.2.2", "eslint-visitor-keys": "^3.4.3", "espree": "^9.6.1", "esquery": "^1.4.2", "esutils": "^2.0.2", "fast-deep-equal": "^3.1.3", "file-entry-cache": "^6.0.1", "find-up": "^5.0.0", "glob-parent": "^6.0.2", "globals": "^13.19.0", "graphemer": "^1.4.0", "ignore": "^5.2.0", "imurmurhash": "^0.1.4", "is-glob": "^4.0.0", "is-path-inside": "^3.0.3", "js-yaml": "^4.1.0", "json-stable-stringify-without-jsonify": "^1.0.1", "levn": "^0.4.1", "lodash.merge": "^4.6.2", "minimatch": "^3.1.2", "natural-compare": "^1.4.0", "optionator": "^0.9.3", "strip-ansi": "^6.0.1", "text-table": "^0.2.0" }, "devDependencies": { "@babel/core": "^7.4.3", "@babel/preset-env": "^7.4.3", "@sinonjs/fake-timers": "11.2.2", "@wdio/browser-runner": "^8.14.6", "@wdio/cli": "^8.14.6", "@wdio/concise-reporter": "^8.14.0", "@wdio/globals": "^8.14.6", "@wdio/mocha-framework": "^8.14.0", "babel-loader": "^8.0.5", "c8": "^7.12.0", "chai": "^4.0.1", "cheerio": "^0.22.0", "common-tags": "^1.8.0", "core-js": "^3.1.3", "ejs": "^3.0.2", "eslint": "file:../../.cache/yarn/v6/npm-eslint-8.57.1-7df109654aba7e3bbe5c8eae533c5e461d3c6ca9-integrity/node_modules/eslint", "eslint-config-eslint": "file:../../.cache/yarn/v6/npm-eslint-8.57.1-7df109654aba7e3bbe5c8eae533c5e461d3c6ca9-integrity/node_modules/eslint/packages/eslint-config-eslint", "eslint-plugin-eslint-comments": "^3.2.0", "eslint-plugin-eslint-plugin": "^5.2.1", "eslint-plugin-internal-rules": "file:../../.cache/yarn/v6/npm-eslint-8.57.1-7df109654aba7e3bbe5c8eae533c5e461d3c6ca9-integrity/node_modules/eslint/tools/internal-rules", "eslint-plugin-jsdoc": "^46.2.5", "eslint-plugin-n": "^16.6.0", "eslint-plugin-unicorn": "^49.0.0", "eslint-release": "^3.3.0", "eslump": "^3.0.0", "esprima": "^4.0.1", "fast-glob": "^3.2.11", "fs-teardown": "^0.1.3", "glob": "^7.1.6", "got": "^11.8.3", "gray-matter": "^4.0.3", "lint-staged": "^11.0.0", "load-perf": "^0.2.0", "markdown-it": "^12.2.0", "markdown-it-container": "^3.0.0", "markdownlint": "^0.32.0", "markdownlint-cli": "^0.37.0", "marked": "^4.0.8", "memfs": "^3.0.1", "metascraper": "^5.25.7", "metascraper-description": "^5.25.7", "metascraper-image": "^5.29.3", "metascraper-logo": "^5.25.7", "metascraper-logo-favicon": "^5.25.7", "metascraper-title": "^5.25.7", "mocha": "^8.3.2", "mocha-junit-reporter": "^2.0.0", "node-polyfill-webpack-plugin": "^1.0.3", "npm-license": "^0.3.3", "pirates": "^4.0.5", "progress": "^2.0.3", "proxyquire": "^2.0.1", "recast": "^0.23.0", "regenerator-runtime": "^0.14.0", "rollup-plugin-node-polyfills": "^0.2.1", "semver": "^7.5.3", "shelljs": "^0.8.2", "sinon": "^11.0.0", "vite-plugin-commonjs": "0.10.1", "webdriverio": "^8.14.6", "webpack": "^5.23.0", "webpack-cli": "^4.5.0", "yorkie": "^2.0.0" }, "keywords": [ "ast", "lint", "javascript", "ecmascript", "espree" ], "license": "MIT", "engines": { "node": "^12.22.0 || ^14.17.0 || >=16.0.0" }, "_registry": "npm", "_loc": "/home/josie/.cache/yarn/v6/npm-eslint-8.57.1-7df109654aba7e3bbe5c8eae533c5e461d3c6ca9-integrity/node_modules/eslint/package.json", "readmeFilename": "README.md", "readme": "[![npm version](https://img.shields.io/npm/v/eslint.svg)](https://www.npmjs.com/package/eslint)\n[![Downloads](https://img.shields.io/npm/dm/eslint.svg)](https://www.npmjs.com/package/eslint)\n[![Build Status](https://github.com/eslint/eslint/workflows/CI/badge.svg)](https://github.com/eslint/eslint/actions)\n[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Feslint%2Feslint.svg?type=shield)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Feslint%2Feslint?ref=badge_shield)\n
\n[![Open Collective Backers](https://img.shields.io/opencollective/backers/eslint)](https://opencollective.com/eslint)\n[![Open Collective Sponsors](https://img.shields.io/opencollective/sponsors/eslint)](https://opencollective.com/eslint)\n[![Follow us on Twitter](https://img.shields.io/twitter/follow/geteslint?label=Follow&style=social)](https://twitter.com/intent/user?screen_name=geteslint)\n\n# ESLint\n\n[Website](https://eslint.org) |\n[Configure ESLint](https://eslint.org/docs/latest/use/configure) |\n[Rules](https://eslint.org/docs/rules/) |\n[Contribute to ESLint](https://eslint.org/docs/latest/contribute) |\n[Report Bugs](https://eslint.org/docs/latest/contribute/report-bugs) |\n[Code of Conduct](https://eslint.org/conduct) |\n[Twitter](https://twitter.com/geteslint) |\n[Discord](https://eslint.org/chat) |\n[Mastodon](https://fosstodon.org/@eslint)\n\nESLint 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:\n\n* ESLint uses [Espree](https://github.com/eslint/espree) 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)\n2. [Configuration](#configuration)\n3. [Code of Conduct](#code-of-conduct)\n4. [Filing Issues](#filing-issues)\n5. [Frequently Asked Questions](#frequently-asked-questions)\n6. [Releases](#releases)\n7. [Security Policy](#security-policy)\n8. [Semantic Versioning Policy](#semantic-versioning-policy)\n9. [Stylistic Rule Updates](#stylistic-rule-updates)\n10. [License](#license)\n11. [Team](#team)\n12. [Sponsors](#sponsors)\n13. [Technology Sponsors](#technology-sponsors)\n\n## Installation and Usage\n\nPrerequisites: [Node.js](https://nodejs.org/) (`^12.22.0`, `^14.17.0`, or `>=16.0.0`) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)\n\nYou can install and configure ESLint using this command:\n\n```shell\nnpm init @eslint/config\n```\n\nAfter that, you can run ESLint on any file or directory like this:\n\n```shell\n./node_modules/.bin/eslint yourfile.js\n```\n\n## Configuration\n\nAfter running `npm init @eslint/config`, you'll have an `.eslintrc` file in your directory. In it, you'll see some rules configured like this:\n\n```json\n{\n \"rules\": {\n \"semi\": [\"error\", \"always\"],\n \"quotes\": [\"error\", \"double\"]\n }\n}\n```\n\nThe names `\"semi\"` and `\"quotes\"` 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:\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://eslint.org/docs/latest/use/configure)).\n\n## Code of Conduct\n\nESLint adheres to the [JS Foundation Code of Conduct](https://eslint.org/conduct).\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://eslint.org/docs/latest/contribute/report-bugs)\n* [Propose a New Rule](https://eslint.org/docs/latest/contribute/propose-new-rule)\n* [Proposing a Rule Change](https://eslint.org/docs/latest/contribute/propose-rule-change)\n* [Request a Change](https://eslint.org/docs/latest/contribute/request-change)\n\n## Frequently Asked Questions\n\n### I'm using JSCS, should I migrate to ESLint?\n\nYes. [JSCS has reached end of life](https://eslint.org/blog/2016/07/jscs-end-of-life) and is no longer supported.\n\nWe have prepared a [migration guide](https://eslint.org/docs/latest/use/migrating-from-jscs) to help you convert your JSCS settings to an ESLint configuration.\n\nWe are now at or near 100% compatibility with JSCS. If you try ESLint and believe we are not yet compatible with a JSCS rule/configuration, please create an issue (mentioning that it is a JSCS compatibility issue) and we will evaluate it as per our normal process.\n\n### Does Prettier replace ESLint?\n\nNo, ESLint and Prettier have diffent 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://prettier.io/docs/en/install#eslint-and-other-linters) to learn how to configure them to work well with each other.\n\n### Why can't ESLint find my plugins?\n\n* Make sure your plugins (and ESLint) are both in your project's `package.json` as devDependencies (or dependencies, if your project uses ESLint at runtime).\n* Make sure you have run `npm install` and all your dependencies are installed.\n* Make sure your plugins' peerDependencies have been installed as well. You can use `npm view eslint-plugin-myplugin peerDependencies` to see what peer dependencies `eslint-plugin-myplugin` has.\n\n### Does ESLint support JSX?\n\nYes, 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.\n\n### What ECMAScript versions does ESLint support?\n\nESLint has full support for ECMAScript 3, 5 (default), 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, and 2023. You can set your desired ECMAScript syntax (and other settings, like global variables or your target environments) through [configuration](https://eslint.org/docs/latest/use/configure).\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/or rule plugins. If you are using Babel, you can use [@babel/eslint-parser](https://www.npmjs.com/package/@babel/eslint-parser) and [@babel/eslint-plugin](https://www.npmjs.com/package/@babel/eslint-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://tc39.github.io/process-document/)), we will accept issues and pull requests related to the new feature, subject to our [contributing guidelines](https://eslint.org/docs/latest/contribute). Until then, please use the appropriate parser and plugin(s) for your experimental feature.\n\n### Where to ask for help?\n\nOpen a [discussion](https://github.com/eslint/eslint/discussions) or stop by our [Discord server](https://eslint.org/chat).\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://www.twilio.com/blog/lockfiles-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://github.com/eslint/eslint/issues?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://github.com/eslint/.github/blob/master/SECURITY.md).\n\n## Semantic Versioning Policy\n\nESLint 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:\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## Stylistic Rule Updates\n\nStylistic rules are frozen according to [our policy](https://eslint.org/blog/2020/05/changes-to-rules-policies) on how we evaluate new rules and rule changes.\nThis means:\n\n* **Bug fixes**: We will still fix bugs in stylistic rules.\n* **New ECMAScript features**: We will also make sure stylistic rules are compatible with new ECMAScript features.\n* **New options**: We will **not** add any new options to stylistic rules unless an option is the only way to fix a bug or support a newly-added ECMAScript feature.\n\n## License\n\n[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Feslint%2Feslint.svg?type=large)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Feslint%2Feslint?ref=badge_large)\n\n## Team\n\nThese folks keep the project moving and are resources for help.\n\n\n\n\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
\n\n\"Nicholas
\nNicholas C. Zakas\n\n		\n\n\"Milos
\nMilos Djermanovic\n\n
\n\n### Reviewers\n\nThe people who review and implement new features.\n\n
\n\n\"唯然's
\n唯然\n\n		\n\n\"Nitin
\nNitin Kumar\n\n
\n\n### Committers\n\nThe people who review and fix bugs and help triage issues.\n\n
\n\n\"Bryan
\nBryan Mishkin\n\n		\n\n\"Francesco
\nFrancesco Trotta\n\n		\n\n\"Yosuke
\nYosuke Ota\n\n		\n\n\"Tanuj
\nTanuj Kanti\n\n
\n\n### Website Team\n\nTeam members who focus specifically on eslint.org\n\n
\n\n\"Amaresh
\nAmaresh S M\n\n		\n\n\"Strek's
\nStrek\n\n		\n\n\"Percy
\nPercy Ma\n\n
\n\n\n\n## Sponsors\n\nThe following companies, organizations, and individuals support ESLint's ongoing maintenance and development. [Become a Sponsor](https://opencollective.com/eslint) to get your logo on our README and website.\n\n\n\n

Platinum Sponsors

\n

\"Chrome \"Automattic\"

Gold Sponsors

\n

\"Salesforce\" \"Airbnb\"

Silver Sponsors

\n

\"Liftoff\" \"American \"Workleap\"

Bronze Sponsors

\n

\"ThemeIsle\" \"Anagram \"Icons8\" \"Discord\" \"Transloadit\" \"Ignition\" \"Nx\" \"HeroCoders\"

\n\n\n## Technology Sponsors\n\n* Site search ([eslint.org](https://eslint.org)) is sponsored by [Algolia](https://www.algolia.com)\n* Hosting for ([eslint.org](https://eslint.org)) is sponsored by [Netlify](https://www.netlify.com)\n* Password management is sponsored by [1Password](https://www.1password.com)\n", "licenseText": "Copyright OpenJS Foundation and other contributors, \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/or 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" }, "artifacts": [], "remote": { "resolved": "https://registry.yarnpkg.com/eslint/-/eslint-8.57.1.tgz#7df109654aba7e3bbe5c8eae533c5e461d3c6ca9", "type": "tarball", "reference": "https://registry.yarnpkg.com/eslint/-/eslint-8.57.1.tgz", "hash": "7df109654aba7e3bbe5c8eae533c5e461d3c6ca9", "integrity": "sha512-ypowyDxpVSYpkXr9WPv2PAZCtNip1Mv5KTW0SCurXv/9iOpcrH9PaqUElksqEB6pChqHGDRCFTyrZlGhnLNGiA==", "registry": "npm", "packageName": "eslint", "cacheIntegrity": "sha512-ypowyDxpVSYpkXr9WPv2PAZCtNip1Mv5KTW0SCurXv/9iOpcrH9PaqUElksqEB6pChqHGDRCFTyrZlGhnLNGiA== sha1-ffEJZUq6fju+XI6uUzxeRh08bKk=" }, "registry": "npm", "hash": "7df109654aba7e3bbe5c8eae533c5e461d3c6ca9" }