I tried using this upgraded dependency (via a yarn dependency resolution) and it seems to have completely broken TypeScript parsing on my project. I get a bunch of "TypeError: p is not iterable" errors as a result.

It seems this was a previously documented issue (#688) and it was fixed in depcheck 1.4.3 by pinning @babel/parser to exactly 7.6.14. There's a related discussion here too (#687).

TL;DR unfortunately it seems that upgrading @babel/parser to 7.21.3 re-introduces this problem :(

Thanks for the comment. I will try to find the fundamental solution.

@jportner I tried to dig more and I believe this PR will not cause the same issue again. because the fix for the root cause is already merged to the main branch with #745

@jportner I tried to dig more and I believe this PR will not cause the same issue again. because the fix for the root cause is already merged to the main branch with #745

Oh I see, that has been merged but not released yet.
I was wondering why your unit test passed!

Thanks for double-checking, and apologies for the false alarm 😄

@rumpl / @jportner do you think we can merge this and get a new release to fix support for TS5? 🙏

As a workaround, if you're using Yarn, you can both peg the resolved version of the Babel parser (a la #788 (comment)) and then yarn patch depcheck to manually patch in the fix to #688, which is thankfully very easy to apply in the transpiled .js.

@znarf @jportner is there any blocker for merging and releasing this? 🙏

@znarf @jportner is there any blocker for merging and releasing this? 🙏

None, I’ll do it this weekend when I get back from my PTO

Thanks for merging this @rumpl 🙏
Do you think we can do a release containing this change? 🙏

I'm also waiting for this change to be released 🎉 thank you!

Thank you for fixing this. Looking forward to the release 🙏.

@rumpl thanks a lot for your efforts.
I could see some changes merged to main, yet no release created since last year!
Is there any issue regarding the same?