How to improve ESLint performance. #7839
christopher-buss
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I use cspell with eslint as I have a custom eslint config that I can install once, and have an easily reproducible tool for all my linting needs. The problem currently is that the cspell plugin takes roughly 1/3 of the entire ESLint time. I understand the issue with async rules and hope this can be fixed, but for now, I'm curious about how best to approach this.
I was thinking I could disable eslint in-editor, and then only use it in git hooks/CI to minimise the cost of the plugin, but I still want spellchecking. From what I can tell, there's no way to get the VSCode extension to 1:1 mimic what ESLint can see - if I could, I could just run the extension on top and then use this as the async plugin.
Beyond this, are there any "best practices"/"performance guides" for setting up cspell correctly to get the most out of this plugin? E.g. disabling certain parts in CI only!
Beta Was this translation helpful? Give feedback.
All reactions