mini-css-extract-plugin: Cannot run lint or test suite; always fails on lint:prettier
- Operating System: Windows 10
- Node Version: 10.x
- NPM Version: 9.6
- webpack Version: -
- mini-css-extract-plugin Version: -
Expected Behavior
When developing a pull request and using npm run lint or npm run test the linter or full test suite is run and reports correct results without false positives.
Actual Behavior
When the lint:prettier task is hit, it results in all scanned files being marked as modified - even though they are not.
How Do We Reproduce?
Check out the plugin’s repository on a Windows system.
Do not make any code changes. Only execute npm run lint or npm run test.
Watch the lint:prettier task still generate a long list of differences and then exit with error code 1, blocking the remainder of the linting or test suite from running.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 32 (21 by maintainers)
There are a lot of guide for for beginners about organization repos, please read them before you start arguing, it makes no constructive thoughts. Also you can send a PR in free style and when fix problem based on CI report or you can leave as is and ask the contributors to fix it, because you can’t do it yourself, there is nothing shameful
I have no idea what the issue is but I think
eol=lfmakes lots of sense for text/code files. If you really need crlf for some files, then override those specifically. Butautouses whatever line ending the OS uses, so that doesn’t seem like a good choice unless someone uses an editor that doesn’t work well with different line endings.