-
-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dist/onig.wasm not available in 0.11.0 #337
Comments
Hrm, there's no docs on how to deploy shiki, so it's very possible that I shipped it wrong - will take a look |
It should autodeploy if a PR bumping the version is merged |
(sorry, low on time today, will look tomorrow) Yeah, I thought that would be it ( https://github.com/shikijs/shiki/runs/7785870097?check_suite_focus=true#step:8:304 ) but it failed for what I think are access token issues |
Fixed in 0.11.1 - thanks for the report! |
Thanks for the work and the great library! |
In our app we use
shiki.setCDN('https://unpkg.com/shiki/')
, and the code that loadsdist/onig.wasm
is redirecting from https://unpkg.com/shiki/dist/onig.wasm to the new https://unpkg.com/shiki@0.11.0/dist/onig.wasmBut this path doesn't seem to exist in the 0.11.0 release: https://unpkg.com/browse/shiki@0.11.0/dist/
Is it intentional that there's no
dist/onig.wasm
in the latest version? I can't see anywasm
files at all in the latest version. The code seems to still be trying to loaddist/onig.wasm
on the latest version: https://github.dev/shikijs/shiki/blob/33ae6b97eda78484460ac05b3338bc72a605194a/packages/shiki/src/loader.ts#L52The text was updated successfully, but these errors were encountered: