This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-07
Channels
- # announcements (3)
- # beginners (124)
- # calva (60)
- # cider (81)
- # cljs-dev (65)
- # cljsrn (1)
- # clojure (268)
- # clojure-dusseldorf (2)
- # clojure-europe (3)
- # clojure-italy (9)
- # clojure-losangeles (1)
- # clojure-nl (22)
- # clojure-russia (3)
- # clojure-spec (24)
- # clojure-uk (34)
- # clojurescript (72)
- # code-reviews (8)
- # cursive (20)
- # datomic (32)
- # fulcro (49)
- # jobs (1)
- # jobs-discuss (15)
- # juxt (10)
- # lein-figwheel (10)
- # nrepl (4)
- # off-topic (37)
- # overtone (1)
- # portkey (2)
- # protorepl (8)
- # random (1)
- # re-frame (1)
- # reagent (43)
- # reitit (8)
- # ring (16)
- # ring-swagger (2)
- # rum (6)
- # shadow-cljs (63)
- # specter (2)
- # testing (32)
- # tools-deps (32)
- # unrepl (1)
- # vim (3)
hey @claudiu, how is your router lib different from the dynamic router in the incubator?
@U6Y72LQ4A Hi. Yep it's a bit different in scope and approach. Currently it's more of a proof of concept, not really production ready.
Working on a big update to it (changing the interface a bit), and getting close to something more stable and with less dependencies.
@U6Y72LQ4A Sorry was a bit tired and misread the question. The fulcro router in icubator is mostly around screen routing of components + intial load. What I am going for is an approach to abstract away stuff like: html5 routing, pre-loading route content, page metadata + painless SSR with all of these (on nodejs now). Think the approach in incubator might be better for admin apps... my main focus is to make my life as easy as possible for simple public apps, that need SEO, code splitting, updating html title etc...
What does this part in documentation exactly means: 2.2.2. Starting the Server Simply start a REPL and use:
I have at least two options:
1) lein repl in project directory
2) connect to nrepl server that is listening at 9000 port (according to npx shadow-cljs server
output)
lein repl in project directory is for a clojure repl, backend server
nrepl port 9000 is for a browser connected clojurescript repl
what exactly do you want to do?
which tutorial? the book?
ok, just a suggestion it’s a lot easier to help if you provide more context like
i started lein repl
in the project directory and got this output
lorem ipsum
yes you can totally use the browser connected repl from cursive
I've tried and (fulcro.client.primitives/get-initial-state app.ui.root/Root {})
doesn't work
> doesn’t work is not at all useful information, that could mean anything
no offense
when you evaluated that code snippet what did output did you get?
have you seen this video?
what is totally useless?
true it’s a little out of date, the video description says that
BUT all the main ideas are the same
which repl depends on if you want a frontend repl or backend repl
the readme that gets generated with the project has a lot more
### Client REPL
The shadow-cljs compiler starts an nREPL. It is configured to start on
port 9000 (in `shadow-cljs.edn`).
In IntelliJ, simply add a *remote* Clojure REPL configuration with
host `localhost` and port `9000`.
If you're using CIDER
see [the Shadow-cljs User's Guide]()
for more information.
### The API Server
The shadow-cljs compiler starts a server for serving development files,
but you usually will not use it. Instead you'll start your own server
that can also serve your application's API.
Start a clj REPL in IntelliJ, or from the command line:
bash
$ lein repl
user=> (go)
...
user=> (restart) ; stop, reload server code, and go again
user=> (tools-ns/refresh) ; retry code reload if hot server reload fails
The URL to work on your application is then
[]().
Hot code reload, preloads, and such are all coded into the javascript,
so serving the files from the alternate server is fine.
and neither of these two work when it comes to this part of doc:
dev:cljs.user=> (fulcro.client.primitives/get-initial-state app.ui.root/Root {})
ya that didn’t work. if anyone has gotten the inspector to work in an electron app, would love some pointers!
@mss, @wilkerlucio would know more but i see there’s this open issue https://github.com/fulcrologic/fulcro-inspect/issues/43 and it’s not documented in the readme, maybe it’s not ready yet?
its not developed, the issue is mostly to track things I like to do, but no roadmap at this point, it still points to the idea, and if anybody wants to do I can help with some guidance about what needs to be done
in summary it needs some work in the communication layer, and the client implementation comms using websockets
i don’t have a need for it right now, but there’s a good chance i’ll need it for our carwash software eventually, maybe i can help then