Skip to content

eslint-error : Expected linebreaks to be 'LF' but found 'CLRF' #2195

Open

Description

@saurabhmehta1601

Problem

Development on windows system gives eslint error Expected linebreaks to be 'LF' but found 'CLRF'

Or what problem could this idea solve?

should this error be ignored ? or the eslint config be updated to not throw this error ? or fix with npx eslint -- fix

Bug URL with Screenshot[

https://publiclab.org/notes/saurabhmehta1601/12-27-2022/eslinterror-expected-linebreaks-to-be-lf-but-found-clrf

Activity

  1. welcome commented on Dec 27, 2022

    @welcome

    Thanks for opening your first issue here! This space is protected by our Code of Conduct - and we're here to help.
    Please follow the issue template to help us help you 👍🎉😄
    If you have screenshots to share demonstrating the issue, that's really helpful! 📸 You can make a gif too!
    Don't forget to join our PublicLab Gitter channel and our ImageSequencer Gitter Channel for some brainstorming discussions.

  2. shrutisachan08 commented on Jan 11, 2026

    @shrutisachan08

    Hi @saurabhmehta1601 ,
    This issue majorly arises on Windows System due to default CRLF line endings , while ESLint is expected to be configured.
    We can either ,
    Update ESLint Config to allow both LF and CRLF or
    Keep the rule strict and recommend running npm eslint --fix.

    I would like to work on the solution.
    Could you please assign this issue to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions