shadow-cljs
shadow-cljs copied to clipboard
Build status in dashboard becomes "unknown" after page reload
This is a very minor issue and I post it here in case I (or someone else) has the time to make a contribution in the next few weeks.
The status of a build is lost when we reload the page of the dashboard.
Before page reload:

After page reload:

The problem is that the current build state is currently constructed by listening to the event stream which receives the :build-start, :build-complete messages etc. This is currently not stored anywhere server-side where the UI could access it on reload.
I've been meaning to fix this for a while now but as you say it is a very minor thing so I haven't gotten around to it yet.
I'm trying to see if I can get the dashboard running locally, want to understand a bit more about the internals of shadow-cljs :)
I spent some time trying to figure out what's going on, ran across a few issues (added shadow-experiments repo, figured out the need to watch :ui and and also appropriate npm installs everywhere)
I got the dashboard running locally, but looks like tailwind is not running. I'm wondering what are the steps to get tailwind and postcss running, as the ui.css files are not getting generated automatically.

Okay I figured it out using postcss. After installing all the missing dependencies, this worked:
npx postcss src/css/ui.css -o .shadow-cljs/ui/css/ui.css
I am not sure if this is the correct way though!
I'm done for the day haha! Tomorrow I'll be exploring the shadow.cljs.ui.worker.builds to see how grove is working and shadow.cljs.ui.worker.generic/init-data to try and persist the state
The UI build is currently in a bit of a messy state given how experimental everything arround it is. master has the fix for the above issue and I added the missing package.json as well. So you'd run npm run ui-dev to start the postcss process. The shadow-cljs build I start from the CLJ REPL (or the UI itself once that is compiled).