hash-css shouldn't be a build hook

[thheller]

This might come over as nitpicky, but you really shouldn't be using shadow-cljs :build-hooks for hash-css.

A good indicator for when things should be a build hook is if they use build-state. You are not using it at all, so this absolutely should not be a hook. I feel it makes the setup needlessly complicated. I would advise removing that build hook entirely and just instead directly call the function from here

clojure-kamal-example/build.clj

Lines 28 to 34 in 8e1ae36

	(defn build
	"Build an uberjar."
	[_]
	(clean)
	(uber {:uber-file UBER-FILE
	:class-dir CLASS-DIR
	:main-ns MAIN-NS}))

Heck, the whole api.util.build becomes obsolete if you just move the code into build.clj. You could even remove the copy-file hook and just do that from within build.clj.

[thheller]

It is also not great to use copy-file and copying the same file onto itself, as that makes the whole build thing not repeatable.

[abogoyavlensky]

@thheller Hi! First of all, thank you a lot for the Shadow CLJS! Your feedback is greatly appreciated. 🙏

I feel it makes the setup needlessly complicated. I would advise removing that build hook entirely and just instead directly call the function from here

Yes, I agree, will rework this part as you suggested.

It is also not great to use copy-file and copying the same file onto itself, as that makes the whole build thing not repeatable.

Makes sense. I didn't plan to use the build function outside the Docker image build, so overriding the same file wan't seemed to me a problem. It's reproducible at the Docker image level. But in general you are completely right and I'll think about improvements.