Clojurians Log v2
shadow-cljs 2026-10-29
have you seen #C086K1WGFA4? @smith.adriane is building that and it looks pretty slick. i don't know what the difference is from what you're building
looks neat, but way out of scope for what I'm doing. I just wanted a simple web based form editor I can use in other apps that want to edit forms (like the shadow-cljs UI).
it’s never been easier to make software that is very specific to personal use cases. I see interesting delimiter closing decision. Does the highlighting help show the block? And separators between top level forms. It’s neat how easily it is to make software precisely how you want it
yes, its a structural editor basically. cursor highlights the "target" which in case of collection is the entire thing. closing delimiters on the right was a test and I quite like it so far. somehow makes everything look less cluttered since I never look at closers anyway and when on the right I basically don't even see them.
Very nice! Love the floaty closers
take a peek. started using it a bit for some test edits with an actual backend hooked up. far from finished but I quite like it already. https://code.thheller.com/demos/shadow-edit/demo.html
looking good
Is there a build target and set of options that make a self-contained Node script? So I can just copy that file somewhere and have it work just fine, without npm i.
this one maybe>? https://shadow-cljs.github.io/docs/UsersGuide.html#target-node-script
It relies on npm i, not self-contained.
(pretty easy to do with squint + esbuild --bundle --minify as well, perhaps this also works for node-script)?
else I would just choose target :esm and use optimizations simple or advanced
Hmm. Now that I keep thinking about it, I should probably go in the opposite direction, lol. Trying to come up with a nice way to build Firebase functions.
there is a mode yes, but its not well tested and might break for certain things that node-targetted libs sometimes do such as referring to files from their package
for the :node-script build you can set :js-options {:js-provider :shadow} which makes it bundle everything like it normally does for browser builds
dunno what the state of ncc is but I'd still recommend using normal :node-script and letting it post process by more specialized tools
but :js-provider :shadow might just work if its simple packages
Looks very interesting!
kinda weird to be writing the clojure code editor of my dreams, at a time where I'm not supposed to read the code anymore (according to some people). I have attempted this many many times over the years and never got anywhere useful. now with 50% of my 20$ weekly claude budget I can just have it generated. granted I prompted a lot to get it closer to my vision and not total slop. this is turning out way better than I ever imagined. might open source at some point if people are interested. and of course if I don't lose interest tomorrow. honestly would prefer someone else build something like it but so far nobody did. now with demos: https://code.thheller.com/demos/shadow-edit/demo.html https://code.thheller.com/demos/shadow-edit/repl.html