Maybe I'll try that next time. It had to go in to bundled code in node_modules to print some extra debugging data to find the source of the bug. Maybe it could have been captured as a test.
I hate it when it wastes my precious subscription tokens on npm crap. "Replace that shit" is also a go to. Every time I deviate from that I regret it later.
This is why I don't tell it to investigate a problem, but tell it
"increase test coverage around x, focusing on scenario y"
Then it often finds the bug with much less tokens