@timothypratley https://clojurians.slack.com/archives/C08BDAPRA/p1759589101234439?thread_ts=1759524023.682739&cid=C08BDAPRA
Thanks - probably - I'm confused about cljs-dev-tools because there is are both the dev build and a non-dev build so in principle it's possible to want to include it in non-dev and that might have some advantages still when printing to the console 🤷 or maybe it's a nonsensical thing to do. It seems most sensible to only use it with dev for sure.
in the non-dev release the cljs-dev-tools doesn't work
it just prints garbage
ah I see, thanks for clarifying
so when people click cljs-dev-tools you'd have to append .dev to every scittle file. it's just one more dimension to take into account (in this beautiful handy website btw)
👍 I've updated it to work as you described. (you might need to refresh the page to get the new behavior).
great thanks. there's one thing in the UI that confuses me though: the dev build doesn't need to use cljs-devtools per se
it's the other way around: cljs-devtools is only useful in dev mode
so when you click cljs-devtools, dev mode should be switched on. not the other way around
maybe it's fine as it is though, in dev mode you'll always get cljs-devtools. doesn't hurt
Hmmm that's true. 🤔 I think if someone really wanted dev without devtools they can always delete it from the copied snippet pretty easily, whereas when clicking dev mode it might not be obvious that including devtools can improve the output, so it seems like including it should at least be a helpful reminder 🤷