This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-14
Channels
- # announcements (7)
- # babashka (51)
- # beginners (292)
- # calva (37)
- # chlorine-clover (40)
- # cider (5)
- # clj-kondo (83)
- # cljs-dev (26)
- # cljsrn (36)
- # clojure (172)
- # clojure-argentina (5)
- # clojure-austin (1)
- # clojure-australia (9)
- # clojure-europe (3)
- # clojure-france (7)
- # clojure-gamedev (3)
- # clojure-nl (3)
- # clojure-spec (4)
- # clojure-uk (34)
- # clojurescript (46)
- # community-development (1)
- # conjure (26)
- # core-async (28)
- # data-science (2)
- # datascript (2)
- # datomic (61)
- # devcards (3)
- # emacs (7)
- # events (2)
- # fulcro (65)
- # graalvm (57)
- # instaparse (2)
- # juxt (21)
- # luminus (6)
- # off-topic (21)
- # pathom (1)
- # pedestal (15)
- # reagent (1)
- # shadow-cljs (19)
- # spacemacs (3)
- # specter (1)
- # sql (14)
- # unrepl (4)
- # vscode (1)
- # xtdb (1)
- # yada (4)
I wondered if anyone had this issue: I am using tfjs-backend-wasm and it requires a wasm file. When I developping, shadow-cljs does not transfer the *.wasm file from the node_module directory. Anyone knows how to circumvent this behavior? Maybe I am doing something wrong.
shadow-cljs has no support for wasm at all. so totally expected that it doesn't copy wasm files.
Then do you think it would make sense to support the node modules that contains WASM files?
once there is a settled standard for wasm maybe. right now each toolchain produces their own variant of JS glue code and includes it differently
until then it would be too much work for me to keep up with all the different ways people handle this
Thanks!
Hi, I'm running a shadow-cljs app, and getting the following error in my browser: WebSocket connection to '<ws://localhost:9631/ws/worker/app/d220add9-aa54-43e3-be71-b121ec13636f/e2fa1a2b-01cf-44e7-9bf0-c5db8cb75503/browser>' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED And the shadow-cljs has stopped reloading, and I don't know what's causing this. How do I even start to debug this, if there aren't any other errors in the console? (edited) Well there's also this error: shadow-cljs: websocket error Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …} bubbles: false cancelBubble: false cancelable: false composed: false currentTarget: WebSocket {url: "<ws://localhost:9631/ws/worker/app/d220add9-aa54-43>…636f/e2fa1a2b-01cf-44e7-9bf0-c5db8cb75503/browser", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …} defaultPrevented: false eventPhase: 0 isTrusted: true path: [] returnValue: true srcElement: WebSocket {url: "<ws://localhost:9631/ws/worker/app/d220add9-aa54-43>…636f/e2fa1a2b-01cf-44e7-9bf0-c5db8cb75503/browser", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …} target: WebSocket {url: "<ws://localhost:9631/ws/worker/app/d220add9-aa54-43>…636f/e2fa1a2b-01cf-44e7-9bf0-c5db8cb75503/browser", readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …} timeStamp: 147976.1250000156 type: "error" proto__: Event
that is not the standard port. so that means there was something else listening on 9630?
could also be your firewall blocking access or your OS having other issues causing it to fail
Or maybe two shadow-CLJS processes?
Do you have a copy of your build file?
Hi, when I build my project in watch mode, everything works fine. But when I build it in release, the compilation works and I get the following error on the start:
shared.js:180 shadow-cljs - failed to load 7
LB @ shared.js:180
shadow$provide.<computed> @ main.js:18
LB @ shared.js:180
$APP.Ho @ shared.js:180
(anonymous) @ main.js:3198
(anonymous) @ main.js:4036
shared.js:180 shadow-cljs - failed to load 11
LB @ shared.js:180
$APP.Ho @ shared.js:180
(anonymous) @ main.js:3198
(anonymous) @ main.js:4036
shared.js:180 Uncaught TypeError: $jscomp.initSymbol is not a function
at Object.shadow$provide.<computed> (main.js:9)
at LB (shared.js:180)
at Object.shadow$provide.<computed> (main.js:18)
at LB (shared.js:180)
at Object.$APP.Ho (shared.js:180)
at main.js:3198
at main.js:4036
Any idea what could be causing this??We have added some npm dependencies, so this could be causing this?
Problem persists when I upgraded to Shadow-cljs 2.8.95.