Closed dcs3spp closed 5 years ago
Apologies to all, I think I understand what was happening....
My npm run lint
script was reporting lint errors/warnings from . (./src/ and ./test). If I altered the lint script to inspect ./src and modified files that are referenced from the entrypoint(s) then the same errors were being reported. At first I had the options failOnError: true, and failOnWarning: true so only one error/warning was being reported at anyone time. When I removed these options then the lint messages started to match up with those reported by npm run lint
script. With webpack I am only operating on the ./src from the entrypoint(s) with no inspection of the tests.
Expected Behavior
Expecting eslint-loader to report the same linting errors as npm run lint. Both reference the same configuration file and extension. The project is a typescript project available here.
Actual Behavior
npm run lint
reports 24 problems within ./src and ./test folders. webpack eslint-loader only reports 3 warnings for unexpected any rule violationsCode
npm run lint script
web.config.common.js
eslintrc.js
tsconfig.json
How Do We Reproduce?
code base is available here