✅ Deploy Preview for shiki-matsu ready!

Name	Link
🔨 Latest commit	2dddd44
🔍 Latest deploy log	https://app.netlify.com/sites/shiki-matsu/deploys/66a07d90bb251f0008046251
😎 Deploy Preview	https://deploy-preview-721--shiki-matsu.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

✅ Deploy Preview for shiki-next ready!

Name	Link
🔨 Latest commit	2dddd44
🔍 Latest deploy log	https://app.netlify.com/sites/shiki-next/deploys/66a07d903803ec000836df11
😎 Deploy Preview	https://deploy-preview-721--shiki-next.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Thank you. While I like esm.sh a lot, it's not the only CDN provider out there, and honestly, it isn't our responsibility to document it on every package - it should be part of the URL convensions.

Thank you. While I like esm.sh a lot, it's not the only CDN provider out there, and honestly, it isn't our responsibility to document it on every package - it should be part of the URL convensions.

If you publish it on jsr, you may not need to consider it. But when I use it in Deno, I would perfer to be able to directly get CDN URL, rather than having to search for each one individually.