Closed aidenlangley closed 2 years ago
Thanks for the report. In the last few weeks we've released vscode-stylelint 1.x, which targets Stylelint 14.x, and 0.x is no longer maintained (migration guide). Is this still an issue you're experiencing with 1.x?
Is it constantly linting my entire repo? Just linting the open file would be preferable.
Speaking for 1.x, the linter runs:
In all these instances, Stylelint itself is only run if the extension's configuration indicates that it should validate a given document. With default settings, for instance, a JS file won't be included in any of the above scenarios.
Closing this now since it's been a week. Feel free to re-open if this is continuing to be a problem. Thanks!
This seems a bit excessive, and I'm tempted to run without the VS Code extension and just lint before building, but this means I'll be backtracking and fixing code when I could be writing lint-passing code at the time.
Is it constantly linting my entire repo? Just linting the open file would be preferable.
My repo is hosted here: https://github.com/aidenlangley/wowhub.co.nz
All configs and code can be found & inspected if you'd like. I'll include my VS code user settings & workspace settings also.
My only user space VS code
stylelint
setting is as follows:My workspace settings, really simple too:
My other extensions
No
v0.86.0
13.13.1
I am using PostCSS & TailwindCSS, here is the config & plugins:
Less fan noise please, less CPU usage.
My laptop is noisier than it ought to be.