This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-11
Channels
- # aleph (38)
- # announcements (6)
- # aws (1)
- # beginners (47)
- # calva (21)
- # cider (47)
- # cljs-dev (18)
- # clojure (40)
- # clojure-europe (7)
- # clojure-india (2)
- # clojure-italy (9)
- # clojure-nl (11)
- # clojure-norway (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (17)
- # clojure-sweden (2)
- # clojure-uk (73)
- # clojurescript (10)
- # cursive (6)
- # datascript (12)
- # datavis (2)
- # defnpodcast (1)
- # duct (5)
- # emacs (36)
- # figwheel (2)
- # figwheel-main (10)
- # juxt (12)
- # leiningen (1)
- # midje (1)
- # nrepl (9)
- # off-topic (25)
- # pedestal (3)
- # portkey (3)
- # quil (2)
- # re-frame (45)
- # reagent (1)
- # ring (3)
- # ring-swagger (36)
- # rum (1)
- # shadow-cljs (48)
- # spacemacs (1)
- # speculative (50)
- # testing (2)
- # tools-deps (27)
- # yada (4)
Does anyone know how to disable the [goog.net.WebSocket] and related logging or at least redirect it to a file or repl? I’m trying to write a reagent-blessed app and it’s messing with the rendering.
http://cl.ly/1eef6fb11adc see how the log messages printing to stdout is interfering with the UI?
Solved it. Posted solution in #clojurescript, turned out not to be directly figwheel related.
Hi, I have a very strange problem: on a minimalist Figwheel Main project, Figwheel stop to work as soon as I add [ring "1.7.1"]
to its dependency. The crash does not happen with [ring "1.7.0"]
. Is this a known problem?
I went to take a look at what changed between the 2 versions, but I did not find anything suspicious except the change of version used. https://github.com/ring-clojure/ring/compare/1.7.0...1.7.1 Is it causing somehow a conflict with the internals of Figwheel Main? If yes, what would be the possible reason?
ah, ok. Thank you!
Sorry, I wrote an issue already https://github.com/bhauman/figwheel-main/issues/140