So, this is the solution:
Locally you can fix it simply by either defining the InspectorURL yourself or load the inspector package yourself beforehand.
2 Likes
So it’s the unpkg striking again 
TBH I don’t remember when we set it to be unpkg instead of our CDN. makes less sense to use unpkg. Might have been during the time that our CDN had some issues, but I am not sure 
Anyhow - this would have been resolved the minute we would have released a new minor verion (tomorrow). Still - we can’t expect people not to use the inspector for a week if something like that has happened.
Thanks a lot for explaining and the help with reproduction. We love learning
1 Like