-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
'extensions' has been removed #251
Comments
Experiencing the same issue - error goes away after downgrading to |
Yeah did the same thing to fix it. Might just need to update documentation in that case if that is the expected behavior. |
Eslint 9 support #250 |
I am still getting this error:
Usinng Maybe only support has been added for versions of |
We are using Webpack 4 which according to the |
Explicit linting is good |
Bug report
Actual Behavior
When using
eslint-webpack-plugin 4.1.0
withwebpack 5.52.1
, I pass an instance of the plugin object to webpack via the plugins array with theextensions
option as follows:However, I receive the error:
My project is using
eslint 9.1.1
. According to the documentation, it looks like theextensions
field is no longer used, which I suspect is the cause of this error.The most recent version with the extensions field is eslint 8.x.
According to the plugin's documentation on NPM:
Expected Behavior
When using
eslint-webpack-plugin 4.1.0
withwebpack 5.52.1
, I expect to be able to pass an instance of the plugin object to webpack via the plugins array with theextensions
option set to lint the correct files.How Do We Reproduce?
eslint-webpack-plugin 4.1.0
,webpack 5.52.1
, andeslint 9.1.1
.ESLintPlugin
(even if theextensions
field is not set, you should still see the error. I assume this is becauseextensions
is still passed to theESLint
object).Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThe text was updated successfully, but these errors were encountered: