Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

Fix: parser interface link #713

Closed
wants to merge 2 commits into from
Closed

Fix: parser interface link #713

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f652f19
Fix: parser interface link
shahroq Apr 20, 2020
bc833d0
change the link
shahroq Apr 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/user-guide/configuring.md
View file
Open in desktop
Expand Up @@ -63,7 +63,7 @@ Setting parser options helps ESLint determine what is a parsing error. All langu
By default, ESLint uses [Espree](https://github.com/eslint/espree) as its parser. You can optionally specify that a different parser should be used in your configuration file so long as the parser meets the following requirements:

1. It must be a Node module loadable from the config file where it appears. Usually, this means you should install the parser package separately using npm.
1. It must conform to the [parser interface](/docs/developer-guide/working-with-plugins#working-with-custom-parsers).
1. It must conform to the [parser interface](/docs/developer-guide/working-with-custom-parsers).

Note that even with these compatibilities, there are no guarantees that an external parser will work correctly with ESLint and ESLint will not fix bugs related to incompatibilities with other parsers.

Expand Down