This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-18
Channels
- # 100-days-of-code (6)
- # announcements (4)
- # beginners (126)
- # cider (49)
- # cljdoc (28)
- # cljsrn (3)
- # clojure (89)
- # clojure-dev (19)
- # clojure-greece (2)
- # clojure-italy (13)
- # clojure-mexico (1)
- # clojure-nl (13)
- # clojure-spec (108)
- # clojure-sweden (1)
- # clojure-uk (48)
- # clojurescript (31)
- # cloverage (3)
- # core-async (16)
- # cursive (28)
- # data-science (3)
- # datascript (1)
- # datomic (60)
- # defnpodcast (1)
- # docker (17)
- # editors (18)
- # emacs (16)
- # events (1)
- # figwheel (22)
- # figwheel-main (4)
- # graphql (26)
- # jobs (2)
- # off-topic (9)
- # om-next (2)
- # overtone (4)
- # perun (1)
- # re-frame (2)
- # reagent (18)
- # reitit (1)
- # ring-swagger (2)
- # shadow-cljs (2)
- # tools-deps (49)
- # uncomplicate (1)
- # unrepl (1)
- # vim (2)
@solussd this worked for me: https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-in-a-Cursive-Clojure-REPL maybe its not appropriate, what is a figwheel.main?
thanks, but I’m using clojure deps (cli tools)
then there is a bunch of editor integration stuff as well starting here https://figwheel.org/docs/editor-integration.html
@bhauman I just figured out what I was doing wrong. 🙂
I’m now starting an nrepl in my user.clj w/ the piggieback middleware and calling figwheel.main.api/start w/ “dev” to get my cljs repl running in Cursive. Works great now– I can evaluate clojurescript line by line.
cider works using the template lein new figwheel testfig -- --reagent
and no changes. What is the
;; for CIDER
;; :plugins [[cider/cider-nrepl "0.12.0"]]
used for?antiquated and not needed. CIDER used to need to have its dependencies in place in the project. it now injects them. That release was at clojure/west in seattle on AuthorDate: Sat Apr 16 13:39:19 2016 -0700
. That sounds like the template might be old 🙂
I'm working on a small app using accountant/bidi for routing/browser URLs and I'd like to have the development server always serve up the index.html at any URL. Should I try to configure Figwheel to do this, or am I stepping outside of it's use case?
eg. http://localhost:3449/ and http://localhost:3449/something-else/ should both serve up my index.html
@ben735 you will want to have a ring handler handle these specific routes and return the index.html
@bhauman thanks, so maybe I make that handler read the index.html file and serve up the contents?