do people use figwheel-main with nodejs?

when I start the nodejs app, I get this error:

[goog.net.WebSocket] Opening the WebSocket on 
INFO [com.nextjournal.renderer:24] - renderer started on 127.0.0.1 : 3000
 [goog.net.WebSocket] An error occurred: undefined
 [  2.184s] [goog.net.WebSocket] An error occurred: undefined
 [goog.net.WebSocket] The WebSocket on  closed.
 [  2.185s] [goog.net.WebSocket] The WebSocket on  closed.
 [goog.net.WebSocket] The WebSocket disconnected unexpectedly: undefined
 [  2.186s] [goog.net.WebSocket] The WebSocket disconnected unexpectedly: undefined
 [goog.net.WebSocket] Seconds until next reconnect attempt: 1
 [  2.186s] [goog.net.WebSocket] Seconds until next reconnect attempt: 1

/Users/kommen/work/nextjournal.com/journal/renderer/compiled/out/renderer/goog/asserts/asserts.js:62
  goog.debug.Error.call(this, goog.string.subs.apply(null, messageArgs));
                   ^
AssertionError: Assertion failed: This browser does not support WebSocket
    at new goog.asserts.AssertionError (/Users/kommen/work/nextjournal.com/journal/renderer/compiled/out/renderer/goog/asserts/asserts.js:62:20)
    at Object.goog.asserts.doAssertFailure_ (/Users/kommen/work/nextjournal.com/journal/renderer/compiled/out/renderer/goog/asserts/asserts.js:121:11)
    at Object.goog.asserts.assert [as assert] (/Users/kommen/work/nextjournal.com/journal/renderer/compiled/out/renderer/goog/asserts/asserts.js:151:18)
    at goog.net.WebSocket.open (/Users/kommen/work/nextjournal.com/journal/renderer/compiled/out/renderer/goog/net/websocket.js:261:16)
    at listOnTimeout (timers.js:327:15)
    at processTimers (timers.js:271:5)

and when I look at the code of figwheel repl, ensure-websocket should ensure to use ws instead of goog.net.Websocket on nodejs: https://github.com/bhauman/figwheel-repl/blob/4dde36a330ef7d0c6008c44ef1425161d4b3581c/src/figwheel/repl.cljc#L451-L464

but ws-connect then just uses goog.net.Websocket after all, which causes the assertion: https://github.com/bhauman/figwheel-repl/blob/4dde36a330ef7d0c6008c44ef1425161d4b3581c/src/figwheel/repl.cljc#L466-L470

I don’t understand though how this is different as with clojure -m figwheel.main -t node -r, which works

turns out, this problem was because the nodejs build was a background build, making it the foreground build makes the problem go away

cc @plexus ^

oh this is interesting, node as a background build should be possible.