-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
parserOptions
shouldn't be in recommended config
#2868
Comments
They definitely should be there, and if you want to set your own parserOptions, that would always be happening after extending configs, so it shouldn't cause any errors. |
No @ljharb he's right; it's incorrect to set Less concerning, but setting |
Order of config extends matters, and the end user should be setting these things anyways. Separately, i don’t recommend using the recommended config from any eslint plugin, including this one - semver constraints mean it’s almost always not in an ideal state. You should be using this plugin via the Airbnb config. |
I think the
parserOptions
options are part of the ESLint config extending fromeslint-plugin-import
or they should be set to the latestecmaVersion
. Using the recommended config leads to errors parsing new JS features like optional chaining.The text was updated successfully, but these errors were encountered: