I'm also seeing this on the next release branch:

[R/T] ✘ AdaptorError: [object Object]

What's going on here is:

• The error is being thrown by tough-cookie deep inside http
• Usually I am hiding stack traces because they're usually out of the user's hands. But it's VERY helpful to see the stack trace on this because I know which part of the adaptor code it comes from, which helps me diagnose the problem.
• The underlying error is a tough-cookie ParameterError. We need to surface that error name, not show AdaptorError
• The actual error message really does seem to be [Object object]. If I used tough-cookie in node and reproduced this, that's what I'd see. So we can't make that bit any better unfortunately.

Some concrete fixes then:

• Include a stack trace in AdaptorErrors
• Use the underlying Error type as the Adaptor Error name