Thank you! In the event you see this may I ask why not stick with Figwheel? Does ShadowCLJS do the job just as well? I remember Figwheel being impressive and it seems maintained.
Figwheel -has- been good for me, but my project is still using the even older figwheel (non-main) rewrite. There hasn't been enough pain to force an upgrade.
From reading and playing with a hello-world project, though, ShadowCLJS seems to offer roughly the same watch|build|hot-reload ability while also offering more and better NPM interop support. As it is now, I have some fairly ugly shell scripting around js packages and builds that could go away if I paid the effort to migrate to ShadowCLJS.
It would also be a lie to say that the generally positive buzz around it doesn't contribute.
If I might ask, what sort of project are you planning?
From reading and playing with a hello-world project, though, ShadowCLJS seems to offer roughly the same watch|build|hot-reload ability while also offering more and better NPM interop support. As it is now, I have some fairly ugly shell scripting around js packages and builds that could go away if I paid the effort to migrate to ShadowCLJS.
It would also be a lie to say that the generally positive buzz around it doesn't contribute.
If I might ask, what sort of project are you planning?