lanjoni
commented
1 month ago Hey Sebastian! I hope everything is going well.
In short, every time you start a new project and run it with shadow-cljs, by default the /dashboard path will always be initialized, after all, it is through this path that you will be able to see your active builds, your active runtimes and your HTTP servers (with their routes). In this case, in the top menu you can see that you can still navigate to builds (where you can force or stop the build of your project), runtimes (where you can explore your active runtime), inspect and inspect-latest to view inspections performed (with taps). The repl-js/browser-repl path is nothing more than an instance of your repl running in the browser, allowing you to evaluate your code and see it being executed in the browser (so you can, for example, evaluate something like (js/alert "hey") and check if it was executed correctly).
The purpose of the dashboard is to provide this broader view and allow you to inspect your project and its active instances in a more pragmatic way. I actually agree with you that perhaps these explanations should be more easily accessible in the Shadow CLJS User’s Guide.
Until then, I would like to say that I actually got to know this dashboard when I was studying Fulcro, in the explanatory videos published by Tony Kay (the attached link is exactly when I first came across this dashboard).
I believe I have understood your question, but if there is any misunderstanding on my part, please correct me. I hope this helps you!
Cheers
SebAlbert
thheller
Hi and thanks for an apparently very cool library!
I just tried starting out on Windows inside WSL2 with the npx quickstart. The WSL2 won't open a browser automagically when I start
npx shadow-cljs browser-repl. Instead I took the terminal output and tried toGET /on the local IP, which redirected me to/dashboard, which only showed "Loading..." and nothing else, with the web-socket connected and sending ping and pong. I spent quite some time trying to figure out what could be wrong.It was only after trying on another machine with a graphical environment where I saw that the automagically opened browser is pointed to a different URL (
/repl-js/browser-repl). Typing this on the first machine with the WSL2 setting also immediately works. If only I had known this earlier. So, bottom line, I think the URL to open in the browser should be printed on the console when starting browser-repl in a vanilla quickstarted project.N.B.: What is that
dashboardanyway? Cannot seem to find that term in the UserGuide anywhere, though there are some closed Github issues containing that term.