it just compile cljs into plain jsx which pandacss's static analyzer can understand. (they can't understand Google closure compiler output)

<Button color={"primary"} hierarchy={"primary"}>primary - primary</Button>
<Button shape={"round"} color={"primary"} hierarchy={"primary"}>primary - primary</Button>
<Button color={"primary"} hierarchy={"secondary"}>primary - secondary</Button>
<Button color={"gray"} hierarchy={"primary"}>gray - primary</Button>
<Button color={"negative"} hierarchy={"primary"}>negative - primary</Button>

@U06LXGPQM5W Thanks for sharing. Could you tell more about how you are you using squint? I also see references to reagent, which doesn't work in squint, so are you using a combination of CLJS and squint or so?

I use shadow-cljs and closure compiler for dev and production build. But panda can't understand it. I create cljsToTsx hook with squint (the code) I preprocess my code (like [button -> #jsx [Button ) before give the code to squint. it's only for pandacss' static analyzer. So the complie output is not runnable. But the panda can track the usage of jsx prop, css and recipe, and generate css file for them.

Impressive :)

Squint is good for js/ts tooling which rely on static analysis. :)