sorry about the brief blip there; turns out we had a caching misconfiguration that prevented client-side JS from loading after an update. it's resolved now and we're fixing the caching to prevent it from happening again.
if you're still seeing issues, try clearing your browser's cache.
had those issues, cleared after a refresh just now, mac firefox. thanks for being on top of it!
thought i fucked something up on my end lol
i just worked around it by archiving it via wayback machine and pasting that into my console, which worked without any issues lol
lmao, big brain. surprised internet archive picked it up tho, the issue was that it was edge-cached incorrectly. maybe their Local Node just hadn't seen it yet, who knows
