Skip to content

Eslint timeout #88

Closed as not planned
Closed as not planned
@Justas-Lapiene

Description

Greetings Folke, love lazyvim.

I noticed that there's a small issue with es-lint though. On bigger projects it basically become unusable, timing out all of the time. I have opted to use eslint_d from mason as its much faster, so the timeouts are less, but it's much less well integrated with lazy as the lazy.extras.eslint. eslint_d sometimes doesn't show errors and sometimes does not provide prettier with the correct formatting configuration.

I work with typescript, so I have been using pnpm lint at the end of my PRs to fix all of the lint problems manually, but honestly that's a little inconvenient.

Is this something you are aware of? is there maybe a way to improve the performance of eslint? I believe it must be something wrong with configuration, as eslint is working fine on the project im working on when im running it in vscode.

Thank you very much for your insights and LazyVim.

Activity

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

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions