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
fantastic, but unfortunately still fairly obscure. Hopefully making it easier to adopt for more use cases will help.
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.
