Hi @Daniel_Garoz,
You shouldn't need to import the library, we did have an incident on cloud related to the moment.js library but we thought it was resolved.
Are you self hosted or on the cloud? I can ping the engineers to look into this incident again. What version of Retool is your instance on?
I just tested this on my cloud instance and the error did not appear, is it still ongoing?
Hi!
It's working now. I was thinking about using the cloud version two days ago. I created a new account to see if it was due to something on my account, but that was happening too. Anyway, it seems to be working again now.
Great to hear! The engineering team was testing out some changes which seem to have inadvertently cause this issue with the moment.js library.
Those changes should be rolled back now with moment working once again!
we began facing unexpected breakages just now due to moment not being recognized as a constructor (TypeError: moment is not a constructor). we have no special setup for loading it, just expecting it "out of the box" as in all our Retool apps.
if i remove the new (and don't treat it like a constructor) then all is good, but for some reason this is what we were doing for like a year+ with no issues.
i'd be curious to know whether the library itself was updated to disallow this pattern, or something else. (i'm fully aware that this might've been an off-label usage that was just tolerated/allowed by the library or Retool runtime, but i'm still curious if anyone knows the details!)
we're on Cloud v3.239.0-734d7b1 (Build 261670)
