This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-29
Channels
- # aleph (4)
- # architecture (12)
- # bangalore-clj (1)
- # beginners (87)
- # boot (3)
- # cider (19)
- # cljs-dev (84)
- # clojars (10)
- # clojure (79)
- # clojure-italy (7)
- # clojure-nl (19)
- # clojure-russia (10)
- # clojure-spec (9)
- # clojure-uk (55)
- # clojurescript (64)
- # core-async (7)
- # core-typed (4)
- # cursive (7)
- # data-science (2)
- # datomic (8)
- # devcards (6)
- # docs (1)
- # duct (5)
- # fulcro (117)
- # graphql (1)
- # instaparse (1)
- # leiningen (13)
- # lumo (103)
- # nyc (3)
- # off-topic (54)
- # om (9)
- # onyx (1)
- # pedestal (6)
- # planck (3)
- # portkey (7)
- # re-frame (26)
- # reagent (20)
- # ring-swagger (14)
- # shadow-cljs (164)
- # sql (11)
- # tools-deps (25)
- # yada (1)
@dnolen guess we would have to do that here?? https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/cli.clj#L396
@bhauman https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/cli.clj#L623, no?
but maybe this is better https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/main.clj#L52
I'm thinking it's add hoc, first obtain a failure signal, then do something, checking leiningen
yeah its add hoc, hook the report function and gather the number of failures to make a decision how to exit
its just that we don't have the ability to supply an exit value from the javascript env
I was going to introduce an exit signal in figwheel and that would solve the general situation
this was a good exploration, I'm going to add the ability to signal figwheel to system exit
stepping back a bit - one thing is we could think about is beforeunload
or something like that for browser process termination detection
yeah, it would be good to solve this problem, everyone's using node based test runners, mainly to get the right exit signal.
and actually I don’t think the browser termination is something to bother with - I keep forgetting that refreshing the browser w/o losing REPL is an acceptable tradeoff
I need to mess around with headless-chrome - that’s probably something we should just supporrt
the more I reflect on the notion of an --main-async
, the more it makes sense given the nature of Javascript and the variety of platforms. The env could provide a completion-callback as the first arg to (defn -main-async [callback & args])
it’s not something that we do in Clojure and I don’t see what we would really get out of it in ClojureScript
async browser tests, other clojurescript tasks that are async in nature and run in the browser, hitting an api from an actual browser environment, etc