Josh Goebel

Another idea (if we go this more ambitious route) is constantly saving the code into the URL (vs local storage) as a `#hashtag` so that problematic code can be tested,...

I think the new website makes this redundant, yes? https://highlightjs-web.herokuapp.com/demo

Sorry this took so long to resolve - please don't feel bad. (I'm glad you're smiling) If you see room for improvement on the new site's similar feature I'm sure...

> The release does not include a JavaScript version. This is intentional, if you want web ready assets use the [cdn-assets](https://www.npmjs.com/package/@highlightjs/cdn-assets) package instead. > Also, the recommended install instructions is...

It's mentioned there. If you'd like to suggest how to make it pop a bit more a PR would be welcome.

Well, it's problematic because I don't want to deal with getting the exact correct HASH in the README every time we bump the version... I've already taken special care that...

Our release process is currently dependent on tagging releases in git. I worry about a GHA modifying the very tag that it's releasing and then retagging it over and over....

> If we changed anything perhaps we could add a small subsection that has a very short introduction to SRI, showing an example (sans hash or HASHGOESHERE) then links out...

> but they should be disabled @marcoscaceres What about something like sample.skip.txt vs sample.expect.txt for cases like this? The tests would look fro both and if it found a skip...

I'm all for a little flexibility here but I'm not sure what all Mocha allows regarding output during tests, reporting, etc.