Closed rozsival closed 3 years ago
We are having the exact same issue since a couple of days ago.
webpack.config.js
new ESLintPlugin({ extensions: ['js', 'jsx', 'ts', 'tsx'] })
package.json
"eslint-webpack-plugin": "^2.1.0"
This solved it for us for now:
--- "eslint-webpack-plugin": "^2.1.0
+++ "eslint-webpack-plugin": "~2.1.0
Hi @rozsival, @eggei Resolved v2.3.0 If the problem persists, reopen this
Since
v2.2.0
the plugin fails webpack build if any package insidenode_modules
referenceseslintConfig
in itspackage.json
but the config itself is actually missing as it is not part of the published npm package.This happens for example with
popper.js
ortippy.js
packages. Ifv2.1.0
of this plugin is used, there is no issue.Expected Behavior
The plugin should ignore missing
eslint
configs of packages insidenode_modules
.Actual Behavior
Webpack build fails because of missing
eslint
config insidenode_modules
package that references it.Code
Inside
webpack.config.js
(simplified for purpose of this issue)Error stack trace
How Do We Reproduce?
webpack@4.44.2
eslint@7.12.1
eslint-webpack-plugin@2.2.0
tippy.js@6.2.7
(will also install@popperjs/core@2.2.4
as a dependency)tippy.js
into a bundle