-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing the linebreak-style eslint error for Windows #171
Comments
Adding a This file configures the editor to add an You might also be interested on a React UI toolkit library I'm working on. |
I'm using atom. Do I have to wire it up somehow to make that take effect? |
Atom natively supports this feature (see this issue): Summary: |
You can also run You might also be interested on a React UI toolkit library I'm working on. |
------------------for windows globe in package.son will read all import files---add-- |
after change your .eslintrc.js to this:
};
|
In User settings for the Vscode search crlf, and adjust your settings. |
I've got the same problem, it was due by the git configuration. when I commited file il the given branch, eof lf was radicaly changed into crlf. look out this link.. https://eslint.org/docs/2.0.0/rules/linebreak-style |
I'd the same problem. In the .eslintrc.json file change "line-break-style" to "unix". As CRLF is for Windows and LF is for unix |
I was told that CRLF is for Linux and LF is for windows @ghost |
@RobFosterNYC - The The Setting the |
If problem persists, try this, but with "ESLint" instead "eslint" |
Simply include this rule to your .eslintrc.js |
What about Mac? |
You can also run npm run lint -- --fix to get rid of the current CRLF |
This solution worked for me |
On Windows, with the current eslint setup, you get this error:
Expected linebreaks to be 'LF' but found 'CRLF'
.The eslint site says this is because Unix and Windows have two different linebreaks.
Is there a better way to fix this besides adding
"linebreak-style": 0,
to the.eslintrc
file?The text was updated successfully, but these errors were encountered: