What that usually means is that you have lines ending with something other than a carriage return/line feed pair. It often happens when you copy and paste from a web page into the code editor. Normalizing the line endings is just making sure that all of the line ending characters are consistent. It prevents one … Read more
Just for a more complete answer, this worked best for me: Replace with in entire solution with “regEx” option. This will set the correct line ending in all files which didn’t have the correct line ending so far. It uses the negative lookahead to check for the non-existance of a \r in front of the … Read more
The only specific reasons to set autocrlf to true are: avoid git status showing all your files as modified because of the automatic EOL conversion done when cloning a Unix-based EOL Git repo to a Windows one (see issue 83 for instance) and your coding tools somehow depends on a native EOL style being present in your file: for instance, a code generator hard-coded to detect native EOL … Read more
Check if you have the linebreak-style rule configure as below either in your .eslintrc or in source code: Since you’re working on Windows, you may want to use this rule instead: Refer to the documentation of linebreak-style: When developing with a lot of people all having different editors, VCS applications and operating systems it may occur that different line endings … Read more
153 I believe my answer covers your new concerns about handling any type of line endings since both “\r\n” and “\r” are converted to Linux standard “\n” before parsing the lines. To support the “\r” EOL character along with the regular “\n”, and “\r\n” from Windows, here’s what I would do: Of course this could be a bad idea on very large files since it means … Read more