Clojurians Log v2

There were in fact API changes. Looks like I could upgrade to 9.3 without any change in the visibility of the graph. Then I could update to 10.9 without triggering error messages, but my graphs became invisible. Which seems more like an effect of a syntax change.

That's about all the time I have for this session; I will be trying again Monday, and hopefully I can get a nice clear report out of what errors happen in which contexts under what version/syntax conditions.

When I just yolo'd the change to 11.6, I saw things like

invalid module
Hide Stacktrace (1 lines)
shadow$provide[110]/</x/bb/Mb</J.onload@https://storage.clerk.garden/nextjournal/clerk-assets@2WtVkTBNZA213UdQKZmWTVuF7TUJ/viewer.js?immutable=true:2298:322

Hey, my good friend Claude and I figured out what was going on. One thing that interfered with debugging was my problem domain happens to like dots in node names, which newer versions of Mermaid are strict about not liking. But the real issue was that in Mermaid v11, • `.render` is now asynchronous and returns a Promise, not a string or callback result. Here's https://www.perplexity.ai/search/i-have-organization-problems-r-T61mCv.HSK24JAyT770tYA, which ends with a summary at the end. I'll fork Clerk and try to formulate this into a merge request. Yay!

I returned to this today. I've found that, • {:package ["mermaid@9.4.3/dist/mermaid.js"]} can be used with no console errors or graph changes • {:package ["mermaid@10.1.0/dist/mermaid.js"]} results in a console error. One reason was, the cdn serves mermaid.min.js instead of mermaid.js. But that's not the only reason.

I'm going to take a break and then see if I can twiddle the :package data to get a working request

"mermaid@10.2.0/dist/mermaid.min.js" to match https://www.jsdelivr.com/package/npm/mermaid?version=10.2.0 yields

dunno what that implies

but it appears to be the same behavior as I step through a couple of point releases. I think maybe this is where there is a syntax change

I get a different error if I leap in time to 11.6.0; I still think it's syntax change related rather than some weird caching thing

Working hypothesis is, I tested updating my syntax to a 10-compatible style, not realizing that jsdelivr also went from serving mermaid.js to mermaid.min.js

And if I update my syntax to 10/11 style, things will work

Alas.

Perhaps if I knew how to use uhhhh what's it called, source mapping?, then I could say something more. But I'm stumped. It could be that that string is not actually the same graph in v9 and v11 syntax, and an LLM lied(!) to me.

At least I think I've ruled out my graph->mermaid transformer being the culprit. I cannot, offhand, think of another mermaid viewer where I could change the version to test that the test string is really simple enough to be independent of version 🤷🏻

can you get it working outside of clerk?

No problem, and this is 11.6 I see

ok, also in a js playground where you’re using the same url as you are in clerk?

I don't know how to do that. I have not used a js playground for anything.

could try on https://squint-cljs.github.io/squint/ for example

I’ll try to find the time tomorrow

I did try in the sense of putting some code into this playground but I'm very far from understanding the levels at work https://squint-cljs.github.io/squint/?boilerplate=https%3A%2F%2Fgist.githubusercontent.com%2Fborkdude%2Fcf94b492d948f7f418aa81ba54f428ff%2Fraw%2Fa6e9992b079e20e21d753e8c75a7353c5908b225%2Faoc_ui.cljs&repl=true&src=KGRlZiBhLWdyYXBoCiAgImdyYXBoIExSCiAgICBBW1N0YXJ0XSAtLT4gQltQcm9jZXNzXQogICAgQiAtLT4gQ1tFbmRdIikKCihkZWZuIHJlbmRlci1tZXJtYWlkCiAgW3ZhbHVlXQogICh3aGVuIHZhbHVlCiAgICBbbmV4dGpvdXJuYWwuY2xlcmsucmVuZGVyL3dpdGgtZDMtcmVxdWlyZSB7OnBhY2thZ2UgWyJtZXJtYWlkQDEwLjMuMC9kaXN0L21lcm1haWQubWluLmpzIl19CiAgICAgICAoZm4gW21lcm1haWRdCiAgICAgICAgICBbOmRpdiB7OnJlZiAoZm4gW2VsXSAod2hlbiBlbAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAoLnJlbmRlciBtZXJtYWlkIChzdHIgKGdlbnN5bSkpIHZhbHVlICMoc2V0ISAoLi1pbm5lckhUTUwgZWwpICUpKSkpfV0pXSkpCgoocmVuZGVyLW1lcm1haWQgYS1ncmFwaCk%3D

Everything is possible 😊 Did you check to see if there were big API changes between versions?