Post

That’s huge :) but that’s not a limit I was running it on huge typescript project references monorepo(jira) with focus on my workspace and a single entry point , took me 30 minutes on Xeon something server with 64 gigs ram. But it worked (sorry haven’t profiled what was the main issue there )

Sorry, not sure I follow. What version of Knip are you talking about? Can't be 6.0.0-0 because that's not even out for 30 minutes 😅

Latest 5th

How? Migrating from TS backend → oxc-parser, which unlocks more streamlining. H/t @boshen.github.io & team! Why? TS → Go. The catch? Drop "unused class members" and Node.js v18. Knip will be up to 3x times faster and handle larger codebases. Feel free to give it a shot, install knip@next 🧑‍🚀

The type aware linting is still in alpha tho and chugs a ton of memory. Tried it and reverted back to eslint 10.

Bottom right of Venz, I can read: "6.0.0-0is 1.58 ± 1.52 times lower" I guess it's "faster", no?!

Yeah the amount of time is lower 😅 Venz is a generic charting solution to visualize/compare numbers. Could have some logic to read "faster" for durations indeed!

Omg ! My brain even saw "slower" ! Lol Of course it's lower !!! Well done 😎