-
Notifications
You must be signed in to change notification settings - Fork 50
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
[Feature request] plugin-shiki migrate to use shikiji #12
Comments
Looking for someone to pick this up? I would be happy to help. |
sure, just pick it up. I am really busy with my article |
It doesn't look like I have permissions to assign the issue to myself but I will start working on this. |
Actually, is |
@nruffing As I remember, that plugin has its own highlightLine and language class implementation. I'm not sure if that's compatible with our default theme, or may introduce some breaking change to theme authors. You can investigate a little more about that. |
The breaking changes between shiki and shikiji are documented here. There is a shim build that restores most of them if necessary but there are still a couple potential breaking changes to theme developers (e.g. the It does appear that other than the We might be able to have the plugin use The simple solution here though might be to just leave the shiki plugin as it is, migrate the vuepress docs to use UPDATE: Using |
BREAKING CHANGE: now `langs` option is required, you need to set the languages list explicitly Co-authored-by: meteorlxy <[email protected]>
Clear and concise description of the problem
Shikiji is a pure esm rewrite of shiki, with some improvement.
Suggested solution
Migrate from shiki to shikiji. No need to update the plugin name, as shikiji might become shiki 1.0 in the future
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: