Add support for parser object to parserOptions.parser
#165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes
parserOptions.parser
to allow you to directly specify a parser object.As background, ESLint core is planning a new flat configuration.
https://eslint.org/blog/2022/08/new-config-system-part-1/
The new configuration allows you to specify parser objects directly.
https://eslint.org/blog/2022/08/new-config-system-part-2/#custom-parsers-and-parser-options-are-mostly-the-same
For this reason, there is a possibility that parsers that do not assume module name specification as before will appear.
The changes in this PR are intended to follow the new parser specification method.
However, you cannot use the custom parser provided by the plugin by name. Because the plugin configuration is not accessible from the parser options.
https://eslint.org/blog/2022/08/new-config-system-part-2/#custom-parsers-in-plugins