@thheller it hangs after calling shadow.cljs.devtools.server/start! via a boot task

I’m using shadow to deploy a production build that includes the library, re-frame-firebase. https://github.com/deg/re-frame-firebase. If I run with :optimizations :simple or :advanced, I get the following error.

------ WARNING #1 --------------------------------------------------------------
 File: firebase/app.cljs:1:14

 constant firebase assigned a value more than once.
Original definition at externs.shadow.js:6
--------------------------------------------------------------------------------

main.js:3157 Uncaught TypeError: Cannot set property 'Error' of undefined
    at main.js:3157
    at main.js:15494   Uncaught TypeError: Cannot read property 'main' of undefined
    at window.onload ((index):14)

goog.nodeGlobalRequire=function(path){return false};goog.provide("goog.debug.Error")

@kanwei no idea but the log you posted clearly shows that you have some dependency conflicts which may cause issues

ie. version 1.3.0 + 1.3.1 of the linked lib are both on the classpath

likely there are other conflicts

@peter005 thats a warning not an error?

do you have the cljsjs.firebase shim setup correctly?

Hitting some weird issue with an undeclared warning, not sure if it's the cljs compiler or something in shadow-cljs.

(go-loop []
  (let [[[request-spec preload started] result] (<! finished-requests)
        request-took-ms (- (.getTime (js/Date.))
                           (.getTime started))
        latest-ten (cons request-took-ms (take 9 @avg-processing-time-coll))
        avg-processing-time (/ (reduce + latest-ten) (count latest-ten))]
    (when (not preload)
      (do (aset result "took" (+ avg-processing-time 100))
          (js/postMessage result #js [result])))
    (recur)))

Says result is undeclared.

no idea. maybe core.async doesn't like the nested destructure?

Sorry, I should edit that. The issue doesn't happen for this code exactly.

With the data literal it gives the warning. Without it doesn't.

I'm guessing core.async macro maybe gets confused?

Yeah could be the go loop.

163 |           (js/postMessage #js {:result result} (to-array [(aget result "data")]))))
----------------------------------------------^---------------------------------
Use of undeclared Var gsv.worker/result

(js-obj "result" result) does that complain?

Tried (js/postMessage (clj->js {:result result}) (to-array [(aget result "data")])) that works.

didn't consider js-obj, that is less invasive probably. Trying that.

Weird issue though! 😄

@bbss I can reproduce this easily ... will see if its shadow-cljs or upstream

(go (let [a 1]
      (prn a)
      (prn #js [a])
      (prn #js {:a a})))

warns about both #js uses

probably core.async though, no issues without the go

@bbss https://dev.clojure.org/jira/browse/ASYNC-132

@kanwei maybe you are running into this https://dev.clojure.org/jira/browse/CLJ-2414. hard to tell since it seems to be working fine for me

but the example specifically mentions sun.nio.fs.UnixPath and I'm on Windows so that might explain it

@thheller Tnx for pointing me in the right direction. Shim needs some attention.