This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-19
Channels
- # announcements (7)
- # aws (4)
- # aws-lambda (1)
- # babashka (19)
- # beginners (60)
- # calva (9)
- # chlorine-clover (3)
- # cider (15)
- # clj-kondo (17)
- # clojure (34)
- # clojure-czech (1)
- # clojure-europe (96)
- # clojure-nl (2)
- # clojure-uk (46)
- # clojurescript (20)
- # css (4)
- # cursive (58)
- # data-science (3)
- # datascript (3)
- # datomic (42)
- # depstar (30)
- # dirac (4)
- # emacs (1)
- # etaoin (5)
- # events (1)
- # figwheel-main (30)
- # fulcro (6)
- # helix (9)
- # jobs (1)
- # lumo (3)
- # malli (27)
- # off-topic (15)
- # pathom (11)
- # programming-beginners (6)
- # reitit (6)
- # rewrite-clj (11)
- # shadow-cljs (14)
- # sql (1)
- # tools-deps (18)
- # utah-clojurians (3)
is there any way to make :infer-warning
s show up in the shadow-cljs hud? they show up in the stdout, but we’d like to see them in the hud as well
Is there a way to get the browser to reconnect after the shadow-cljs connection has been close?
@wombawomba it should be trying to reconnect on its own?
It doesn’t though… I need to refresh
FWIW this happens whenever my laptop goes to sleep
@kommen they should show up in the HUD just as any other warning? as does :warnings-as-errors
?
I don’t think I’m on the newest shadow-cljs version though.. perhaps this has been fixed in newer releases?
when this happens there’s a red box saying “Connection closed!” where the usual messages go
alright, I’ll try the newest version and see if that fixes it 🙂 thanks
@thheller true that. upgrading from shadow-cljs 2.8.91 to the latest version indeed makes them show up in the hud 🙈
@thheller what is the status on :esm?
I’m looking to spend some time getting NextJS working with shadow-cljs. Looking through your next-cljs project and approach seems straightforward for automation. But for now I’d like to build things out manually to get a feel for how viable this is. Output needs to work in both node and browser. Have tried :esm and :npm-module but get duplicate require issues. Which target is best to try work through? Is this something you would be ok lending some support if I were to build out a proper integration?