Skip to content


docs: remove manually maintained anchors (#16685)
Browse files Browse the repository at this point in the history
* docs: remove manually maintained toc and anchors

* revert: toc is back
  • Loading branch information
kecrily committed Dec 22, 2022
1 parent b401cde commit 8bda20e
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ ESLint is a tool for identifying and reporting on patterns found in ECMAScript/J
2. [Configuration](#configuration)
3. [Code of Conduct](#code-of-conduct)
4. [Filing Issues](#filing-issues)
5. [Frequently Asked Questions](#faq)
5. [Frequently Asked Questions](#frequently-asked-questions)
6. [Releases](#releases)
7. [Security Policy](#security-policy)
8. [Semantic Versioning Policy](#semantic-versioning-policy)
Expand All @@ -41,7 +41,7 @@ ESLint is a tool for identifying and reporting on patterns found in ECMAScript/J
12. [Sponsors](#sponsors)
13. [Technology Sponsors](#technology-sponsors)

## <a name="installation-and-usage"></a>Installation and Usage
## Installation and Usage

Prerequisites: [Node.js]( (`^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.)

Expand All @@ -57,7 +57,7 @@ After that, you can run ESLint on any file or directory like this:
./node_modules/.bin/eslint yourfile.js

## <a name="configuration"></a>Configuration
## Configuration

After running `npm init @eslint/config`, you'll have a `.eslintrc` file in your directory. In it, you'll see some rules configured like this:

Expand All @@ -78,11 +78,11 @@ The names `"semi"` and `"quotes"` are the names of [rules](

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the [configuration docs](

## <a name="code-of-conduct"></a>Code of Conduct
## Code of Conduct

ESLint adheres to the [JS Foundation Code of Conduct](

## <a name="filing-issues"></a>Filing Issues
## Filing Issues

Before filing an issue, please be sure to read the guidelines for what you're reporting:

Expand All @@ -91,7 +91,7 @@ Before filing an issue, please be sure to read the guidelines for what you're re
* [Proposing a Rule Change](
* [Request a Change](

## <a name="faq"></a>Frequently Asked Questions
## Frequently Asked Questions

### I'm using JSCS, should I migrate to ESLint?

Expand Down Expand Up @@ -141,15 +141,15 @@ We intentionally don't lock dependency versions so that we have the latest compa

The Twilio blog has a [deeper dive]( to learn more.

## <a name="releases"></a>Releases
## Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a [release issue]( for updates about the scheduling of any particular release.

## <a name="security-policy"></a>Security Policy
## Security Policy

ESLint 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](

## <a name="semantic-versioning-policy"></a>Semantic Versioning Policy
## Semantic Versioning Policy

ESLint follows [semantic versioning]( 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:

Expand Down Expand Up @@ -182,7 +182,7 @@ ESLint follows [semantic versioning]( However, due to the na

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.

## <a name="stylistic-rule-updates"></a>Stylistic Rule Updates
## Stylistic Rule Updates

Stylistic rules are frozen according to [our policy]( on how we evaluate new rules and rule changes.
This means:
Expand All @@ -191,11 +191,11 @@ This means:
* **New ECMAScript features**: We will also make sure stylistic rules are compatible with new ECMAScript features.
* **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.

## <a name="license"></a>License
## License

[![FOSSA Status](](

## <a name="team"></a>Team
## Team

These folks keep the project moving and are resources for help.

Expand Down Expand Up @@ -278,7 +278,7 @@ YeonJuan


## <a name="sponsors"></a>Sponsors
## Sponsors

The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. [Become a Sponsor]( to get your logo on our README and website.

Expand All @@ -291,7 +291,7 @@ The following companies, organizations, and individuals support ESLint's ongoing
<p><a href=""><img src="" alt="launchdarkly" height="32"></a> <a href=""><img src="" alt="Nx (by Nrwl)" height="32"></a> <a href=""><img src="" alt="Anagram Solver" height="32"></a> <a href=""><img src="" alt="VPS" height="32"></a> <a href=""><img src="" alt="Icons8: free icons, photos, illustrations, and music" height="32"></a> <a href=""><img src="" alt="Discord" height="32"></a> <a href=""><img src="" alt="ThemeIsle" height="32"></a> <a href=""><img src="" alt="Ignition" height="32"></a> <a href=""><img src="" alt="HeroCoders" height="32"></a></p>

## <a name="technology-sponsors"></a>Technology Sponsors
## Technology Sponsors

* Site search ([]( is sponsored by [Algolia](
* Hosting for ([]( is sponsored by [Netlify](
Expand Down

0 comments on commit 8bda20e

Please sign in to comment.