I’m wondering if this realistic in practice: usually with CLJS, you wouldn’t call the result from the top-level like that

Rather, you’d like define the namespace, then the loading page would kick off some “main” function, which would then eventually call result

And I generally wouldn’t expect hot-reloading to actually run code like result, but rather just reload all your functions, etc

I realize that’s not a great answer, but I’m wondering if in practice what you have is actually “working” for a realistic use case

In any case - I think this is fundamentally something I don’t understand about shadow or CLJS or onerror handlers.

I’m far from the expert on those topics 😦 , so my advice is maybe to ask in #clojurescript and see if anyone has solved this. I am 99% sure this doesn’t relate to Expound though - you could reproduce the same problem by omitting the call to (set! spec/*explain-out* expound/printer) and I expect you still wouldn’t see a plain-ole spec error printed

Or, even more explicitly, if you changed your code to be something like this

(defn error-handler [message url line column e]
  (print "???????????????????????????????????????????")
  (js/console.error e)
  (print (repl/error->str e))
  true)

Yes you're right, it has nothing to do with whether Expound is being called. It's that (set! (.-onerror js/window) error-handler) doesn't seem to take effect right away.

I'll look into that. I guess I have two one parting questions, if you don't mind!

1. Why do I see <filename missing>:<line number missing> at the top of the Expound error from my screenshot? Those would be awfully useful to have.

2. Even with the setTimeout call, I still can't get the Devtools error formatter to work. Does window.onerror also need to be set for that, or should this code (from the README) be enough? EDIT: Disregard this. I've realized it does indeed work, however only with setTimeout. I get the result from the photo below.