Hey folks,
We noticed this one too and it thankfully resolved itself.
Thanks for reporting it @RWelch!
We're investigating what looked to be a transient issue with how frontend assets are delivered to your browser. The issue auto resolved after the next iteration of that asset set was published.
I can't provide much further information, but we're looking into how we can ensure it doesn't happen again.
Whilst I am a Meraki employee, some of what I post may be opinion (especially architecture!). Others may have better or more efficient ways of doing things, so please learn from everyone!