@alexmiller seems I don't have access to transit-js anymore? I tried to push a fix for the Closure breaking changes

@dnolen don't think that was any intentional change, but could easily have been switched in a cleanup, I will figure out how to get you back in there

thanks!

invite sent - that should give access to all the transit repos

thanks!!

@dnolen ping me if there are releases needed on core.async or transit stuff

@alexmiller core.async would be nice \cc @mfikes

@alexmiller there was a lot of bitrot in transit-js - I went and patched things up to latest Closure / Closure-Library

JS consumers aren't actually much affected by Closure breaking change because they just consume released stuff - i.e. advanced compiled thing

but we will need a transit-js maven release - and when that's done, a bump to transit-cljs

and release

CI for transit-js would be nice, let me know if it's ok to add a GH workflow thing-y

it would just run the tests

definitely ok by me, although not sure if it will work in the account it's in (there is some long story there that I don't know most of, but I may not have latest info). would be ok to try it and see!

corehttp://core.aIasync under wayhttp://core.aI will look at transit-js and transit-cljs release later - may take some setup to get -js release working again for me

https://ask.clojure.org/index.php/10524/whats-with-this-difference-between-reading-uuids-between-cljs

answered, but mostly because I don't know what is going on there

2 versions of ClojureScript at least - both old-ish