Justin Searls

Yeah, agree, we probably shouldn't throw a mystery meat boolean at an unrelated-looking method. I think this is the right approach. Is console.log/warn the right mechanism for getting folks that...

Thanks @connorjclark! Tagging in @giltayar because he understands this better than I do.

> where the user is surprised that no mocking occurs even if mocking is requested, is more problematic than the latter. We should leave it at that! Yes, at the...

Interesting. Since [quibble](https://github.com/testdouble/quibble) is a separate module, I wonder if you're pulling in a bundled/browserify'd build of testdouble.js? Unsure what's happening

Interesting! Other than tagging @giltayar for help, I wonder if this issue also exists under Windows under the latest Node 16.13.0?

@RexMorgan thanks for looking into this. I think that a PR that used a more durable pattern (or, if Windows _always_ behaves this way, even for network shares, a branching...

Seems good

Is throwing any ol' not-error-but-object-that-has-a-`message`-property some legit pattern that I hadn't heard about?

ah, clever! I think that makes sense. Have you spiked to confirm that this would work?

Dayum, that is some interesting detail on Node's console's `inspect` contract. We should totally take advantage of this for `td.explain`