Clojurians Log v2

Is it different from the one I tried earlier?

I'm not sure, probably not much, but would be good to double-check before I make a release later today. I'm also wondering if this is the best setup (naming everything .dev) while duplicating the build. Another way we could do it could be a /dev folder. Maybe this would be easier (at least for me); now I copy-pasted the whole build config and appended .dev to each module...

Right, I'll try. I think that a separate dir makes more sense, especially if it's easier for you. Then switching to dev could be a matter of changing a single route on the server.

ok, this is what it's going to look like. please test again if you can.

new commit also pushed to branch

In the archive, the cljs-devtools file still has dev in its name. Do the files in the archive not have the stacktrace changes? I opened that reproduction when some JS function is nil while being called inside a JS event handler, and only the intermediate CLJS function is mentioned, with just a single entry in :sci.impl/callstack.

it does, but in a JS event handler it doesn't work :-( I'll change the cljs-devtools name and put a release. incremental improvements after that

Alright, cool.

Huh, but it seems to work in js/setTimeout. Well, there's no pretty message, but at least the reported line is accurate and there are two callstack items.

ah crap I didn't bump SCI

third release...

try scittle@0.7.26 on npm now (not considering the stack improvements though, just the dev build stuff)

Ah, alright, that does bring back that missing line in the callstack. BTW, is there a way to pass some custom config to cljs-devtools on the user end? A call back to https://clojurians.slack.com/archives/C034FQN490E/p1755135377651389?thread_ts=1755019363.681209&cid=C034FQN490E.

here's the release: https://github.com/babashka/scittle/releases/tag/v0.7.26 I'll come back to your question later...

Dang this is so cool! I'm confused about the purpose of /dev. Is it to release stuff that's not yet ready for prod for people to test? Or will we always have to load from the /dev path when using devtools?