Heya, I was trying to reproduce and understand what's happening in https://clojure.atlassian.net/browse/CLJS-2992 It looks like GCC is declaring a local variable that shadows the GCC namespace object, which then causes local assignments to not use the real namespace object I'm unsure of what code was originally generated by https://clojurescript.org/guides/javascript-modules as the steps in that example doesn't seem to work anymore (it throws java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter). Does anyone have some pointers for me to continue looking into this?

@filipematossilva to be clear :npm-deps stuff (which was always of alpha quality) isn't super high priority any more

I would consider that ticket to be a really advanced one too - you will need to understand the interaction between Closure & ClojureScript pretty well

that said if you're determined look at cljs.build-api-tests

I thought we had es6 module tests, maybe we need more

I'm assuming you're ignoring the versions discussed in the ticket and using the latest

yes, I am using latest

to be honest I'm mostly just looking for stuff I can help in within my skillset... if this isn't very relevant I'm happy enough to look at other things

@filipematossilva I think we have a newbie tickets tag - I would start there

just get something small in and get used to the process

ah cool, I see that now

https://clojure.atlassian.net/browse/CLJS-2924?jql=project%20%3D%20CLJS%20AND%20status%20in%20(%22In%20Progress%22%2C%20Open%2C%20Reopened)%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20newbie%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

will take a look, thanks!

np

We are coming up on 2 years since checked arrays (https://clojurescript.org/news/2017-07-14-checked-array-access) Maybe it should default to :warn at some point? (I'd guess all of the popular libraries have now been updated.)