Performance of single package reporting about knip HOT 7 CLOSED

Sure, I'll cherry-pick those commits into canary & publish today!

from knip.

Published: https://github.com/webpro/knip/releases/tag/4.0.0-canary.8

from knip.

Thanks for posting this. Is this about v4? Otherwise I prefer not to spend my time on it. Please try v4 canary and see what diff that makes.

from knip.

Ah, it's v3. I can check the v4 as well!

from knip.

V4 report here: processed2.txt (markdown reporter was not usable in v4 yet)

V4 time: 7.66s user 1.54s system 99% cpu 9.214 total
V3 time: 7.86s user 1.69s system 123% cpu 7.724 total

Not so much difference in execution time between the versions though there are some improvements for V4 visible. Randomly the time is longer for both but that's normal, it's around 7-8 seconds for this one package usually with both versions.

Seems like most of the time both v3 and v4 is going to read the files in SourceFileManager::getSourceFile so not sure if there's much to do about it.

from knip.

Yes, no surprises here. Performance is generally much better when linting a monorepo as a whole (as opposed to per workspace separately). Also see https://knip.dev/blog/slim-down-to-speed-up for some additional background.

from knip.

Alright thanks, any chance to get the markdown reporter also included in the canary? I think backstage could start using the canary version then because at the moment only the dependency checks are enabled from knip.

from knip.