Remove extra parens when no stacktrace available.

[jenanwise]

weasel.repl/process-message for :eval-js currently tries to call the string "No stacktrace available" when processing an error with no stacktrace. This results in a new error and the repl hanging. Instead it should just return the string as a value, which would match the behavior of clojure.browser.repl/evaluate-javascript.

[tomjakubowski]

thanks!

[the-kenny]

Is there a chance to cut a new release for this? I'm running in this error quite often in conjunction with primatic/schema.

[tomjakubowski]

@the-kenny Just released 0.2.1 with this fix and a related one.

Out of curiosity, where does it happen that a js/Error object lacks the stack property? Older versions of IE? Some kind of manually constructed Error in a promise library?

[the-kenny]

No browser at all. It's caused by prismatic/schema when the validation of a schema via validate fails.

[tomjakubowski]

Prismatic seems to throw ExceptionInfo objects rather than native js/Error objects in some circumstances. Apparently these ExceptionInfo objects don't have a stack property, although I'm seeing one (albeit not a very useful one) in my tests. If I recall extending the native js/Error object like that can lead to some weird behavior.

I did notice that the error message for these doesn't include the bit of useful extra data passed to ex-info:

cljs.user> (throw (ex-info "foo" {:key-a 123 :key-b 456}))
#<Error: foo>
No stacktrace available.

so I opened an issue which I plan to tackle soon: #13