I disagree. Errors that cause library files to fail to load are serious problems and I think we want to make it easy for developers to find them, and throwing the error to the page they tried to load is the fastest way to communicate the error. You just made the change that created the error, now will be the easiest time to fix it.
You are unlikely to be able to fix the error in the UI since you created it by breaking a file. The reload changed files is a developer feature and should not be used on production sites.
I will file a TIP for this.
best,
Carl
