Document fast code reload
alexslade opened this issue · 4 comments
(Firstly, thanks for creating this, I've found it very useful in getting started with CLJS development!)
The process for reloading code as I understand it takes a long time. Running the tests via the browser REPL is great, but then code isn't reloaded which makes it less useful. I assume I'm missing something there; if that's the case then some examples should be added to the docs.
Happy to do PR if can point me in the right direction.
Hi Ales, thnx for the very appreciated offer to collaborate. As you probably know at the moment cljs developing are going forward very frequently in the area of simplifying the developing process. I would wait a little bit to better understand the consequences of the amazing work by David Nolen and probably a little bit of stability in the cljs-repl, cljsbuild and cljs.test area. But we could start thinking about the objective of the cljs-start itself. What we want to offer to clojurescriptist, both in the browser area (browsers JS) and in the server area (nodejs). In my opinion it should be a tool tohelp starting to develop cljs libraries and cljs/node application by reducing the complexity of setting up a dev/devops environment with batteries included. what you think about this?
My best
mimmo
I agree that "batteries-included starter package" is a good goal :)
I'm totally new to CLJS development, and I've been a bit suprised to find that things are very hard to get started with. I'm a developer of ~10 years, so it's mainly a matter of learning the clojure + cljs ecosystems and approaches, but it's still very hard for a fresh developer to get started.
My previous message was more of a question: what's going wrong? Why aren't fast-reload tests a thing? I wrote some simple tests using my own code and just printed the results to the broswer console (which, using figwheel, is nearly instant) so I assume that it's not hard to actually achieve.
I would love to see cljs-start be that guide for new developers, while still being very useful as a quickstart for experienced ones.
Hi Alex, even if you are totally new to CLJS, your long experience with other languages/ecosystem is very valuable in defining at least the objectives of this lein-template. As I said in this period CLJS ecosystem is evolving rapidly and I still have to get into them.
Could we try to set together few objectives for this lein-template? Could you please write down a list of the requirements you would want to see in this lein-template and which in your opinion replicate the best experiences you had with other languages/ecosystem?
thanks for the hints!
mimmo
Off the top of my head:
A basic placeholder app should be produced that has:
- More than one namespace (seems simple, but was a big stumbling block for me personally)
- Tests, that run quickly. Ideally on file save.
- CSS and JS that reloads. Perhaps the tests are run this way in the browser? Not sure of the best way to do this.