oh doh. breakage is no fun.

you could also just take the deleted https://github.com/google/closure-library/blob/b1f269132288b4959db97408dd0e1fb84f6fa8d7/closure/goog/net/cookies_deprecated.js file and put it into your classpath

at least it should be found that way

For the time being, we pinned shadow-cljs back to 2.21, at least to give us some breathing space. Good idea that we could put the shim back in. I feel that it would be nice if we can donate a fix to reagent-utils though.

> Does anyone know if reagent-utils is being actively maintained? Would raising an issue, or going further and putting a pull request together, get me anywhere? Can't comment for this particular lib but I'd say that raising an issue is always worth it. Even if it doesn't necessarily solve your problem, it will show other people that the library might not be worth using.

Raised https://github.com/reagent-project/reagent-utils/issues/21 and started working on a pull request.

out of interest @U05224H0W why did shadow bump the closure library version, previously it matched the version used by the clojurescript compiler, but now it seems to be diverging?

maybe it was this issue https://clojurians.slack.com/archives/C07UQ678E/p1677514340671429

indeed it was

fwiw shadow-cljs generally follows the closure-compiler much quicker than regular CLJS. mostly because I make much more use of it due to the whole npm integration. so generally it is best to also somewhat keep up with the closure-library

I made a https://github.com/reagent-project/reagent-utils/pull/22 and it has already been merged \o/

why the dynamic thing?

because the existing tests were using set! to switch in a stub for the deprecated goog.net.cookies so I changed the test to use a binding instead

very happy to make further changes if you have better ideas

Heh, seems like in CLJS, binding actually results in those set!, interesting.