This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-27
Channels
- # bangalore-clj (1)
- # beginners (187)
- # braveandtrue (52)
- # calva (7)
- # cider (17)
- # cljs-dev (14)
- # clojure (27)
- # clojure-austin (4)
- # clojure-dev (11)
- # clojure-finland (4)
- # clojure-italy (5)
- # clojure-nl (1)
- # clojure-russia (22)
- # clojure-spec (9)
- # clojure-uk (27)
- # clojurescript (91)
- # datomic (40)
- # duct (4)
- # emacs (14)
- # figwheel-main (36)
- # fulcro (11)
- # hoplon (10)
- # immutant (9)
- # instaparse (4)
- # java (1)
- # jobs (2)
- # off-topic (28)
- # pedestal (1)
- # reagent (15)
- # reitit (7)
- # remote-jobs (6)
- # ring-swagger (3)
- # shadow-cljs (28)
- # slack-help (1)
- # spacemacs (4)
- # specter (1)
- # sql (3)
- # testing (3)
- # tools-deps (24)
hey folks, is it possible to use figwheel in a standalone webserver ? I have web application which is using pedestal and I want to integrate figwheel with it
@bhauman so in conclusion, I need to serve the compiled assets through my application and run the figwheel repl too. Then I should be able to connect to figwheel repl through my webserver am I right ?
@lxsameer the first part is right. But figwheel will still run its own server, and the web application will connect back to the figwheel server’s websocket to provide REPL support
ok and the CORS headers set by the figwheel server. should i change any configuration to let the application connect to a different address for websocket ?
I saw the issue in 0.1.7 and for me it's fixed in 0.1.8
@pesterhazy are you the person who told me he uses devcards alongside the normal build?
@bhauman hmm... I use devcards with figwheel.main, but I can't remember if I told you that
no, I didn't know about background builds
I was using it before extra mains for sure, but I just used the main build
currently devcards is the main ui (it's a playground app)
I'll definitely check out extra mains once I do more work on it