This is a good reminder that I need to extract and open source the Shiki integration stuff from my personal site. I doubt I fully addressed the limitations in the linked issue, as my usage is fully static (both build and runtime), but there are other parts people might find useful: mapping inline styles to unique generated class names for more generalized styling (currently depends on Fela for atomic classes, but can be generalized further), which also enables support for light/dark mode without JS. Shiki is <i>fantastic</i>, but unfortunately still fairly obscure. Hopefully making it easier to adopt for more use cases will help.<p>I also agree that tree-sitter is a pain to use in web projects, but I’ll be open sourcing my solutions for that too (either as direct contributions to web-tree-sitter where appropriate, or as plugins for ecosystem tooling where I had to do additional work to support specific tools) as it’s part of ongoing, already open source project work.
I use Torchlight (<a href="https://torchlight.dev" rel="nofollow">https://torchlight.dev</a>) for syntax highlighting on a static site (<a href="https://keygen.sh" rel="nofollow">https://keygen.sh</a>) and it’s been great. I use Torchlight’s CLI to precompile the code snippets during the build step. Much better than highlighting client-side with JS.
Out of curiosity, since this post discusses syntax highlighting on the web and supports code syntax highlighting, what blog engine does this site use? Does it support giving headings their own id (I use headings and like being able to refer to them with anchor URLs, but I didn't see any headings on the entire blog)?
Seems similar to twoslash:<p><a href="https://shikijs.github.io/twoslash/" rel="nofollow">https://shikijs.github.io/twoslash/</a><p><a href="https://github.com/shikijs/twoslash" rel="nofollow">https://github.com/shikijs/twoslash</a>