Would it be possible to bump squint in an upcoming cherry release? I got hit by this (https://github.com/squint-cljs/squint/issues/661) today but it looks like squint’s had it handled since May. (I can override in the meantime in package.json, but wouldn’t have realized it was even fixed till I tracked down a minimal repro!)
I bumped squint in the recent release but it introduced another bug unfortunately
Have you tried the most recent version already?
of cherry? yeah it’s still using squint 0.8.141 as best as I can tell, and this bug is fixed only in 0.8.147 if I have that right. I’m tracking down lots of wacky cljc things now that I bumped to 0.8.150 manually which I’m assuming are my fault, unless that’s the new bug
if there’s other bugs to work out, consider my request not a top priority — i can deal in the meantime
are you talking about the squint standard library?
Yeah, I’ve been overriding with a newer squint using “cherry-cljs”: “0.4.29", “squint-cljs”: “0.8.150",
the squint compiler is already bumped in the most recent version. what you have is only the runtime dependency on the squint standard library for HTML generation
but let me bump that too and make a new release since there is another bug that got fixed in the squint compiler. the squint compiler is referenced in deps.edn and compiled to JS
Okey dokey. Will diagnose. I likely have an old cherry in my ball of spaghetti mess that’s being incorrectly referenced. Will try to pin down. Thank you!
published cherry v0.4.30 now
thank you so much! will poke around accordingly.
problem no longer present. many thanks — not sure if it was actually this version bump or just a cleaning out of cached stuff.