We have resolved the issue. It was caused by a recent dependencies update we performed an hour ago. During the update, an unrelated dependency unexpectedly became corrupted, but the resulting errors were delayed. This meant the dashboard continued to function initially but later crashed once the corrupted dependency was called upon. We're sorry for any inconvenience this has caused.