All Runkit embeds are currently broken because of a bad integrity hash !
For example, this if I use this HTML code from the documentation on a page:
<h3 style="text-align: center;">Welcome to my website</h3>
<script src="https://embed.runkit.com" data-element-id="my-element"></script>
<!-- anywhere else on your page -->
<div id="my-element">// GeoJSON!
var getJSON = require("async-get-json");
The embed doesn’t load, and instead I get these errors in the JS console:
Does this reproduce every single time on the computer where it is not working? If so, maybe we could create a reduction (an Ubuntu container where we can get it to happen on our end, etc.). Given that it was happening in Ubuntu yesterday and Windows today, I imagine the answer is no here.
When you inspect the file in the browser that doesn’t work, does the inspector say that this was a successful response (200, is the Content-Length header the smaller or bigger file size, does it show any sort of downloading error, etc.).
Kind of scared to ask this because we might lose the state its in to be able to reproduce this, but you have tried previously to empty the browser cache/etc. and it kept happening? IOW, this isn’t some weird local cache state your browser is in, but something that repeatedly happens in the interaction between the browser and the server?
I’ll update here if I come up with more questions that could help us reproduce this.