papandreou / consider Goto Github PK

Suggested by @sunesimonsen

Currently calling .clone() seems to return an Unexpected clone that escapes the consider wrapping. I discovered this while working on an adapter library that clones internally and uses it to add some assertions that should not be exposed globally.

I think the fix might be to have consider expose a modified .clone() method which clones Unexpected and wraps it before returning so it continues to behave in a consider fashion.

There are only a couple of things preventing using this library on node 4.x:

• 'use strict' declaration will allow the use of let
• ...rest parameters