You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.
introduce a warning from linting, such as no-unused-variables, startup webpack with webpack dev server, and see the warning.
stop webpack dev server, then start again. you will not see the error.
Notes
Without cache-loader, the expected behavior above does happen. i'm not sure if the issue is with cache-loader, or with eslint-loader
@evilebottnawi no, but we need cache-loader for other reasons. The repro repository provided is as bare-bones as necessary to reproduce the issue. In our private corporate repository, we are using cache-loader (among many other dependencies) for a variety of other reasons.
Expected Behavior
with eslint-loader set up to not fail on errors/warnings, and if cache loader is used with babel-loader, warnings/errors should show up consistently.
Actual Behavior
with eslint-loader set up to not fail on errors/warnings, and if cache loader is used with babel-loader, warnings/errors should show up consistently.
Code
How Do We Reproduce?
introduce a warning from linting, such as no-unused-variables, startup webpack with webpack dev server, and see the warning.
stop webpack dev server, then start again. you will not see the error.
Notes
Without cache-loader, the expected behavior above does happen. i'm not sure if the issue is with cache-loader, or with eslint-loader
webpack-contrib/eslint-loader#267
The text was updated successfully, but these errors were encountered: