This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-04
Channels
- # admin-announcements (9)
- # beginners (40)
- # boot (61)
- # cider (6)
- # cljsrn (5)
- # clojure (65)
- # clojure-gamedev (6)
- # clojure-greece (8)
- # clojure-ireland (1)
- # clojure-portugal (5)
- # clojure-russia (46)
- # clojure-uk (38)
- # clojurescript (177)
- # core-async (9)
- # cursive (17)
- # datomic (6)
- # dirac (8)
- # emacs (5)
- # error-message-catalog (8)
- # hoplon (248)
- # ldnclj (11)
- # ldnproclodo (1)
- # lein-figwheel (36)
- # leiningen (12)
- # mount (2)
- # off-topic (3)
- # om (26)
- # onyx (12)
- # perun (2)
- # planck (26)
- # re-frame (62)
- # reagent (55)
- # remote-jobs (2)
- # rethinkdb (1)
- # ring-swagger (14)
- # spacemacs (47)
- # untangled (69)
I followed the guide https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-in-a-Cursive-Clojure-REPL and for project generated by “lein new figwheel” it works basically ok
however, for project generated by “lein new reagent” it doesn’t seem to work well - the figwheel repl is not able to connect to the browser - and I can’t figure why
The issue is also described here: https://github.com/bhauman/lein-figwheel/issues/297
Oddly enough, I if run another figwheel repl via “lein figwheel” in console, the Cursive repl is able to connect - however, after I stop the figwheel running in console and restart Cursive REPL the browser keeps complaining:
ClojureScript has not been compiled!
please run lein figwheel in order to start the compiler
@jumar: The reagent template profile.clj contains a lot of stuff. Maybe start out with the figwheel template instead, and then add the stuff you need when you need?
yeah, that’s definitely an option - however, I just want to try some reagent hello world and check how it works with figwheel
I required [cljsjs.reactable] in a clojurescript namespace. Subsequently hovering over Reactable.Table ( from the required library ) invokes the message "This object cannot be resolved." Otherwise the program works as expected. Is this expected behaviour because it is an external javascript library?
@cfleming: I’m working on the Cursive REPL integration with Dirac: (teaser) https://dl.dropboxusercontent.com/u/559047/the-first-happy-joined-dirac-session-party.png my current problem is that after joining a Dirac session in Cursive (which effectively turns it into ClojureScript REPL), Cursive still thinks it is a normal Clojure REPL. What is the mechanism which determines/triggers Cursive to treat the REPL as CLSJ REPL?
@darwin: It’s done by pattern matching on the output. It’s hard-coded right now, but I had planned to expose that in config.
Currently it searches for "Type :cljs/quit
to stop the ClojureScript REPL” or "To quit, type: :cljs/quit"