Yeah, this is an unfortunate interaction with archive.org trying to be too clever about our Javascript (we send a completely fine HTML version of each page on initial pageload, and then later send the javascript, in large parts to make sure crawlers work, and this seems to work fine for Google and other crawlers, but archive.org tries to load the full JS package, then run it, and then get confused about why running the JS package from a completely separate URL with half of the files missing doesn’t work).
If anyone has a solution to fixing this, I would be glad to help them create a pull request for that on our Github repository.
Yeah, this is an unfortunate interaction with archive.org trying to be too clever about our Javascript (we send a completely fine HTML version of each page on initial pageload, and then later send the javascript, in large parts to make sure crawlers work, and this seems to work fine for Google and other crawlers, but archive.org tries to load the full JS package, then run it, and then get confused about why running the JS package from a completely separate URL with half of the files missing doesn’t work).
If anyone has a solution to fixing this, I would be glad to help them create a pull request for that on our Github repository.