André Mello

Attempted this with #92 but sadly there's no support for testing this kind of feature atm (see https://github.com/mikaelmello/inquire/issues/107 for example). We probably need to restructure the code so we can...

Partially, though less so. A new client is still created for each dependency explored when constructing the dependency graph as part of the `install()` command. I had [a PR](https://github.com/helsing-ai/buffrs/pull/87) that...

Rather than remove, another option is to change them so they are more useful. I get why having high coverage is appealing, it has good marketing value, and open-source projects...

Note this is overlapping with other PRs like #182, but more comprehensive.

BTW I didn't touch the parent script but it's also quite stale (it's got some very old versions on the lockfile, and the travis setup is relying on Node 10).

> For the sake of avoiding misinformation percolating: the only reason it's currently possible to have multiple "installed" recorders is due to the nature of being pre-1.0, and how often...

Are we still moving forward with this @chanced?

Hey, sorry about that, I went through a major redesign with Chance to minimise allocations with that crate. We've still got a few kinks to iron out before getting to...

Also, perhaps this can be closed now that you're on 0.6.x?

Somewhat related, I just noticed `core::error::Error` [was stabilised in 1.81](https://doc.rust-lang.org/stable/core/error/trait.Error.html), so we should track removing the `Error` implementations from the `std` feature flag next time we bump the minimum Rust...