Hello. In my Google Cloud Functions project the deployment broke. shadowcljs compile works, but deployment crashes with:

Error: Error occurred while parsing your function triggers.
TypeError: Cannot read property 'get' of undefined

java.time.Period=java.time.goog$module$goog$object.get(shadow.js.shim.module$$js_joda$core,"Period");

@witek https://clojurescript.org/news/2021-11-04-release looks like you're running into this since shadow upgraded CLJS as well

I believe clj-kondo can audit for these cases now? The other things is :global-goog-object&array compiler flag - you can set this to true to get the old behavior

for the case where the problem is in your dependency which is probably the case

Yep, clj-kondo reports about this

I am using tick... which uses Joda

the problem is likely in tick

https://github.com/juxt/tick/blob/4dbe14a1ea6ea0b31292dbafcd9be620265eab59/src/tick/core.cljc#L1279

The compiler option fixed my issue. Thank you very much. Again! 🙏 ❤️

@witek @borkdude https://github.com/juxt/tick/issues/154 opened a issue

I highly recommend doing this in all projects where it is encountered

Thanks @dnolen - I've pushed a fix to master for that. testing with 1.10.891 I am seeing foreign-lib code is having properties renamed under advanced compilation and so stops working. This is not tick code using foreign code, but actually the foreign code itself. For example in this code from a js lib, the zones property reference of packedJson is renamed. Is there any way to prevent this?

MomentZoneRulesProvider.loadTzdbData = function loadTzdbData(packedJson) {
    TZDB_DATA = packedJson;
    TZDB_VERSION = packedJson.version;

    for (var _iterator = packedJson.zones, _isArray = Array.isArray(_iterator), _i = 0, _iterator = _isArray ? _iterator : _iterator[Symbol.iterator]();;) { 

@henryw374 hrm I would say this is a bit odd - no externs inference test failed (which doesn't prove something regressed but I'm skeptical at the moment)

@henryw374 we dump the inferred externs to a file in the target - if you're using shadow it might happen in a different way

you could compared inferred externs from before / after the release

when porting some code I'm getting a message that the-ns is not in CLJS - is that right?

it's hard to search for answers 🙂

@raymcdermott very few ns / var facilities exist as they are not applicable

and/or porting them isn't practical

ok @dnolen good to know that I'm not missing something obvious

I have a function to obtain metadata about any given var

like this in Clojure

(defn add-metadata
  [ns-name var-name]
  (let [ns-thing (the-ns (symbol ns-name))]
    (binding [*ns* ns-thing]
      (meta (resolve (symbol var-name))))))

@raymcdermott ok, but you shouldn't do that in ClojureSript

no vars, no namespaces

there is one edge case where vars become useful in ClojureScript

but I doubt this applies to what you are doing - and that is lazy loading of code splits

you're right, I'm not doing that

is there another, general way to obtain metadata for functions?

@raymcdermott I think you need to explain a bit what you are doing?

you need to reflect into the compiler to get this stuff - nothing works at runtime

@raymcdermott we haven't done a good job keeping this up-to-date but I just updated some things now - https://raw.githubusercontent.com/clojure/clojurescript/master/devnotes/corelib.org

ah - didn't know about that list 🙂

what I'm trying to do ... inspect the code that somebody is typing into an editor or has pasted in and recognize stuff like meta data. There are heavyweight analysis tools for this but I'm trying to use spec and the core libs to do it all dynamically even if they provide less info.

we don't have time for answering why 😉

asking also here https://clojurians.slack.com/archives/C053AK3F9/p1636144690270900

@raymcdermott I honestly think just using the analyzer would be much easier

All the info you probably need is available