Andrea Richiardi

Not like less, more like: I show you ten, then at the repl either you ask me the other ten or you evaluate the next meaningful command.

My 2c: - I like `powerlaces` because it hints at boot tooling stuff without having it (again?) in the name - I like the version with no group-id - I...

Agree that adding `meta` with clear semantic on what is merged into what, can be a good option (actually the only one left :smile:). About build ids, probably some sort...

isn't that optional? I have a couple of projects without the file and they work fine...

I mean, the user might not know that `boot-cljs-devtools` needs the file...I agree it can be made clear in the README though...

Ok so I will ask the maintainer (or do it myself) to make clear that you need an explicit file. Thanks for the clarification, maybe we can make it clear...

Yeah that's exactly the reason and the reason why I was thinking myself of a more generic method...I am PR-ing the `boot-cljs-devtools` README..

I would make it a first class citizen, promoted to the main README and in Usage as well. It is kind of important :wink:

As creator and former maintainer of `clojurescript.io`...that is not unfortunately not active anymore, but hopefully will stay up (don't have control on it anymore!). The repo could be forked and...

I am glad you referred to macchiato because that's exactly what I contributed to yesterday: https://github.com/macchiato-framework/macchiato-http :smile: