Can you try and update shadow-cljs to the latest version once and see if it fixes this?

I'm running the latest version, maybe i should downgrade?

Can you also check if you have latest https://github.com/lambdaisland/glogi in the deps?

If you don't have an entry feel free to add one explicitly

Let me try

Adding an explicit dependency to glogi gives me The required namespace "goog.debug.LogBuffer" is not available, it was required by "lambdaisland/glogi/console.cljs".

Sorry just one last time to confirm, you are still on latest shadow and cljs versions?

Because I had this exact same error in a project today and updating all deps fixed it 🙈

I downgraded shadow-cljs from 2.17.8 to 2.16.12

Noooooo, try upping it back up 🆙

Cljs is also at latest 1.11.4

let me try again

Can you also run this (assuming you're using deps to manage shadow):

➜  your-project git:(main) ✗ clj -Stree | grep glogi
com.lambdaisland/glogi 1.1.144
  X com.lambdaisland/glogi 1.0.136 :use-top

This is the relevant error: https://github.com/lambdaisland/glogi/pull/20

> Can you also run this (assuming you're using deps to manage shadow): Please also share the exact version of ClojureScript and of google closure library that it's pulling in. We've made a lot of effort in glögi to be compatible with all the different ClojureScript versions but maybe they made breaking changes again, or maybe we're not actually compatible with certain versions.

a full clj -Stree would be great, or if you can't share that for reasons then please share the output of

clj -A:dev -Stree | egrep '(glogi|closure|clojurescript)'

clj -A:cljs:dev-cljs:test-cljs -Stree | egrep '(glogi|closure|clojurescript)'

      X lambdaisland/glogi 1.0.70 :use-top
      X lambdaisland/glogi 1.0.70 :use-top
  X org.clojure/clojurescript 1.11.4 :use-top
  . com.google.javascript/closure-compiler-unshaded v20220202
  . org.clojure/google-closure-library 0.0-20211011-0726fdeb
    . org.clojure/google-closure-library-third-party 0.0-20211011-0726fdeb
  . org.clojure/google-closure-library-third-party 0.0-20211011-0726fdeb
org.clojure/clojurescript 1.11.4
  X com.google.javascript/closure-compiler-unshaded v20210808 :older-version
  . org.clojure/google-closure-library 0.0-20211011-0726fdeb
    X org.clojure/clojurescript 1.10.597 :use-top
      X org.clojure/clojurescript 1.9.89 :use-top
    X org.clojure/clojurescript 1.7.170 :use-top
    X org.clojure/clojurescript 1.7.48 :use-top
    X org.clojure/clojurescript 1.9.908 :use-top
lambdaisland/glogi 1.0.106
  X org.clojure/clojurescript 1.10.238 :use-top

the root of the problem is a series of breaking changes in the google closure library, which has led to us having to resort to increasingly creative hacks to still be able to support all versions, and we do test glogi on multiple versions of clojurescript and thus closure, but as I said either there's a regression or there's been another breaking change

perfect! thanks! let me check that

Sorry for the delay I was in a meeting

> >

lambdaisland/glogi 1.0.106

hmm

There's two different packages

>

lambdaisland/glogi

>

com.lambdaisland/glogi

OH YES! You need the com.lambdaisland/glogi {:mvn/version "1.1.144"} version

yeah was just gonna say, newer releases are under com.lambdaisland for this package to be in line with clojars policy

should i also use the com.lambdaisland for kaocha deps as well?

If available, kaocha is on lambdaisland/kaocha not on com

ok

no, we're still releasing kaocha under lambdaisland. For most projects that already existed before the new policy we're sticking to lambdaisland for now because clojars/tools.deps don't support propert relocation (yet). With glogi we were a bit too fast to move to the new id but then decided to move back and forth would create even more confusion.

Sorry, I'm aware this is a bit of a mess. for background: • https://github.com/lambdaisland/open-source/issues/2 • https://clojure.atlassian.net/browse/TDEPS-8 • https://github.com/clojars/clojars-web/issues/801

I see, i just saw kaocha-cljs under the new org and I assumed everything was migrated

Anyways i'm happy to inform you that it finally built

great! happy to hear! we would like to migrate everything, but until clojars and tools.deps have a better story for that we're afraid it's going to cause too much churn.

newer packages are only released under com.lambdaisland, because we are no longer allowed to publish those under lambdaisland

I see