Skip to main content

Deploys for shiki-next

shiki.style

Published main@f8ef446

Deploys

  • Production: main@f8ef446 published

    chore: migrate `minimist` to `cac`

    Deployed in 2m 28s

  • Deploy Preview #964: custom-twoslasher@d868e85 completed

    feat(vitepress-twoslash): add option for custom twoslasher

    Deployed in 3m 30s

  • Production: main@83b6794 completed

    chore: release v3.2.1

    Deployed in 3m 12s

  • Production: main@ef6f296 completed

    chore: release v3.2.0

    Deployed in 2m 46s

  • Production: main@2914137 completed

    chore: update deps and js report

    Deployed in 2m 42s

  • Production: main@b11c684 completed

    feat: upgrade deps, new langs and themes

    Deployed in 2m 23s

  • Deploy Preview #960: quansync@59fe0c3 failed

    feat: use `quansync` to support async transformer and on-demand loading

  • Deploy Preview #960: quansync@348e4ef failed

    feat: use `quansync` to support async transformer and on-demand loading

  • Production: main@05ccf77 failed

    docs: update CDN shiki version to v3.0.0 (current) (#958)

  • Production: main@3bbd82a completed

    fix: faild to run shiki doc server locally (#959)

    Deployed in 2m 42s

  • Production: main@fdf376f failed

    test: migrate to monorepo exports snapshoting

  • Deploy Preview #960: quansync@717f88d failed

    feat: use `quansync` to support async transformer and on-demand loading

  • Production: main@ece4b02 failed

    test: snapshot public exports

  • Deploy Preview #959: docs@96cc4cd completed

    fix: failed to run shiki docs server locally

    Deployed in 1m 27s

  • Deploy Preview #959: docs@afb2494 completed

    fix: failed to run shiki docs server locally

    Deployed in 1m 21s

Collaborate, test, build…

Every time you open a pull request, or push new changes to a branch, Netlify automatically builds a preview with a unique URL. Like a staging environment for every PR or branch, deploy previews are perfect for testing and collaboration.

Join Netlify or log in if you already have a Netlify account to browse the full deploy history for this site.