scittle

timothypratley 2025-10-04T20:27:27.388219Z

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.

borkdude 2025-10-04T20:28:09.680789Z

in the non-dev release the cljs-dev-tools doesn't work

borkdude 2025-10-04T20:28:16.859379Z

it just prints garbage

timothypratley 2025-10-04T20:28:39.647049Z

ah I see, thanks for clarifying

borkdude 2025-10-04T20:29:30.961159Z

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)

timothypratley 2025-10-08T21:26:50.204079Z

👍 I've updated it to work as you described. (you might need to refresh the page to get the new behavior).

borkdude 2025-10-08T21:28:34.070629Z

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

borkdude 2025-10-08T21:28:50.850899Z

it's the other way around: cljs-devtools is only useful in dev mode

borkdude 2025-10-08T21:29:06.917169Z

so when you click cljs-devtools, dev mode should be switched on. not the other way around

borkdude 2025-10-08T21:32:48.012829Z

maybe it's fine as it is though, in dev mode you'll always get cljs-devtools. doesn't hurt

timothypratley 2025-10-08T23:09:12.629459Z

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 🤷

👍 1