This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-01
Channels
- # admin-announcements (1)
- # beginners (16)
- # boot (22)
- # cider (96)
- # clojure (146)
- # clojure-dev (5)
- # clojure-germany (7)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-japan (76)
- # clojure-russia (6)
- # clojure-seattle (1)
- # clojure-sg (1)
- # clojure-uk (19)
- # clojure-ukraine (1)
- # clojurescript (114)
- # code-reviews (11)
- # datomic (42)
- # editors (4)
- # euroclojure (3)
- # jobs (18)
- # ldnclj (59)
- # off-topic (1)
- # om (17)
- # reagent (5)
- # yada (43)
In the meantime you can use this: https://github.com/danielsz/boot-environ
samflores: I’ve gotten bitten like you. core.match and sente’s deadly encounter. I’ve stuck with [org.clojure/core.match "0.2.2”]
, but alandipert’s chops are too righteous.
i wonder about a database where we can collect known-problematic combinations and a task for querying it with your deps
alandipert: would be awesome, especially given the amount of time spent on debugging in theses situations.
yeah 😦
samflores: BTW, if you use sente and boot, maybe you should have a look at https://github.com/danielsz/sente-system.
actually I already looked several of your gh projects 😄 https://github.com/danielsz/sente-boot was the base of my current configuration
samflores: Cool. Yeah, there’s no absolute imperative to componentize dependencies, but if you want interactive development at the REPL, you need some sort of plan
There is a node cljs test runner but it's a bit old
@jthomson: it's not especially structured, but the smoke test for splint.js uses HTMLUnit WebClient to run cljs https://github.com/adzerk-oss/splint.js/blob/master/build.boot
thanks @mitchelkuijpers @alandipert I'll see how I get on with those