You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my current project introducing stylelint raised watch build time from ~3s to ~25s. I guess, it happened because of big amount of files and amount of rules.
So, maybe we could cache files that failed to lint on initial run and then include them + files that changed for linting. That should decrease overhead from linting all the files that passed initially and hasn't been changed.
It seems this will require slight update how to deal with stylelint formatter, because in order to get failed files it would require both JSON and string output.
If this suggestion sounds good, I'd be happy to poke around and apply the optimization.
The text was updated successfully, but these errors were encountered:
sergesemashko
changed the title
Performance optimization suggestion, lint only initially failed files + changed files
Performance optimization suggestion, lint only failed files + changed files
Jan 5, 2017
On my current project introducing stylelint raised watch build time from ~3s to ~25s. I guess, it happened because of big amount of files and amount of rules.
So, maybe we could cache files that failed to lint on initial run and then include them + files that changed for linting. That should decrease overhead from linting all the files that passed initially and hasn't been changed.
It seems this will require slight update how to deal with stylelint formatter, because in order to get failed files it would require both JSON and string output.
If this suggestion sounds good, I'd be happy to poke around and apply the optimization.
The text was updated successfully, but these errors were encountered: