I haven't been catching up, how's cljs support going with polylith?
Can confirm what Mitchel said, we might be hitting the 3 months even 😛 . I think the hardest part for us was figuring out how we need to manage our JavaScript dependencies. We are bundeling our front- and back-ends so all node dependencies need to be available on the project level, but newer JavaScript package manager expect the the dependencies to be isolated. We have it working now, but that did take us a bit.
Good question! The plan is to fix a few more open issues that are not related to cljs support, and then continue with the cljs support.
The cljs-support branch seems to work, but we need to update the realworld example project and the documentation:
• Split frontend code into several components in https://github.com/furkan3ayraktar/clojure-polylith-realworld-example-app/tree/cljs-frontend branch in the realworld example.
◦ Make some components cljc to demonstrate code share between frontend and backend (the entire frontend is under web-ui component at the moment).
◦ Update README to explain
▪︎ How both frontend and backend work together
▪︎ How to share code between frontend and backend
▪︎ How to start locally
▪︎ How to deploy
▪︎ How to run tests
• Update the poly tool documentation.
• Update the high-level documentation
◦ Explain our choice of going with shadow-cljs with tools.deps as recommended build tool
◦ ...and more
Right now I'm working on non-cljs stuff (open issues) and at some time I will do a 0.2.22 release, before continuing with the cljs support.
So the functionality is ready, and what is left is documentation. Can't wait for the ultimate unification! haha
Yes, everything should be in place, except maybe for a test runner for cljs.
Just FYI we have been using this branch for the past 2 months with multiple frontends and nodejs backends and it works rock solid.