You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -41,7 +41,7 @@ ESLint is a tool for identifying and reporting on patterns found in ECMAScript/J
41
41
12.[Sponsors](#sponsors)
42
42
13.[Technology Sponsors](#technology-sponsors)
43
43
44
-
## <aname="installation-and-usage"></a>Installation and Usage
44
+
## Installation and Usage
45
45
46
46
Prerequisites: [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.)
47
47
@@ -57,7 +57,7 @@ After that, you can run ESLint on any file or directory like this:
57
57
./node_modules/.bin/eslint yourfile.js
58
58
```
59
59
60
-
## <aname="configuration"></a>Configuration
60
+
## Configuration
61
61
62
62
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:
63
63
@@ -78,11 +78,11 @@ The names `"semi"` and `"quotes"` are the names of [rules](https://eslint.org/do
78
78
79
79
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/user-guide/configuring)).
80
80
81
-
## <aname="code-of-conduct"></a>Code of Conduct
81
+
## Code of Conduct
82
82
83
83
ESLint adheres to the [JS Foundation Code of Conduct](https://eslint.org/conduct).
84
84
85
-
## <aname="filing-issues"></a>Filing Issues
85
+
## Filing Issues
86
86
87
87
Before filing an issue, please be sure to read the guidelines for what you're reporting:
88
88
@@ -91,7 +91,7 @@ Before filing an issue, please be sure to read the guidelines for what you're re
91
91
*[Proposing a Rule Change](https://eslint.org/docs/developer-guide/contributing/rule-changes)
92
92
*[Request a Change](https://eslint.org/docs/developer-guide/contributing/changes)
93
93
94
-
## <aname="faq"></a>Frequently Asked Questions
94
+
## Frequently Asked Questions
95
95
96
96
### I'm using JSCS, should I migrate to ESLint?
97
97
@@ -141,15 +141,15 @@ We intentionally don't lock dependency versions so that we have the latest compa
141
141
142
142
The Twilio blog has a [deeper dive](https://www.twilio.com/blog/lockfiles-nodejs) to learn more.
143
143
144
-
## <aname="releases"></a>Releases
144
+
## Releases
145
145
146
146
We 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.
147
147
148
-
## <aname="security-policy"></a>Security Policy
148
+
## Security Policy
149
149
150
150
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](https://github.com/eslint/.github/blob/master/SECURITY.md).
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:
155
155
@@ -182,7 +182,7 @@ ESLint follows [semantic versioning](https://semver.org). However, due to the na
182
182
183
183
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.
Stylistic 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.
188
188
This means:
@@ -191,11 +191,11 @@ This means:
191
191
***New ECMAScript features**: We will also make sure stylistic rules are compatible with new ECMAScript features.
192
192
***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.
These folks keep the project moving and are resources for help.
201
201
@@ -278,7 +278,7 @@ YeonJuan
278
278
279
279
<!--teamend-->
280
280
281
-
## <aname="sponsors"></a>Sponsors
281
+
## Sponsors
282
282
283
283
The 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.
284
284
@@ -291,7 +291,7 @@ The following companies, organizations, and individuals support ESLint's ongoing
0 commit comments