-
-
Notifications
You must be signed in to change notification settings - Fork 30
Plugin requires "parserOptions.sourceType" being configured to "script" #244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
not sure I got your point. is it related to |
The short answer is that the plugin requires I'm more than happy to contribute a PR to add to the documentation if we see fit. |
sure, PRs are always welcome! 👍 |
One important note here: as mentioned at the top of our README, eslint-plugin-eslint-plugin can work on all CJS/ESM/TypeScript repos, so either There were some general improvements I wanted to make to the usage example in the README, so I opened a PR #245, and also mentioned |
I had searched in the repo, it does not check |
Our plug-in doesn't specifically care what sourceType is. I think what he's running into is just general eslint syntax parsing issues. |
@bmish I think you hit the nail on the head. I'll add a comment to the PR as you asked 👍 |
Rules in this repo have a dependency on eslint being configured with:
This is makes sense, but I ran into unexpectedly as I created a plugin from scratch rather than using the yeoman generator (https://github.com/eslint/generator-eslint).
For context, using the generator
eslint-plugin-node/recommended
gets extended and this config sets the parserOption).Can we update the documentation somewhere to make it clear that this is a configuration requirement?
I'm happy to create a PR to update
README.md
with this.The text was updated successfully, but these errors were encountered: