Skip to content

feat: rename shiki packages #3506

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

Merged
merged 1 commit into from
Jan 27, 2024
Merged

feat: rename shiki packages #3506

merged 1 commit into from
Jan 27, 2024

Conversation

antfu
Copy link
Member

@antfu antfu commented Jan 26, 2024

A full round circle, and now we are back to Shiki :P

The v1.0.0-beta.0 is the exact same implementation as the latest Shikiji, it shouldn't make any difference to end users.

The only breaking change is that shikijiSetup is renamed to shikiSetup (it's easy to provide soft deprecation, but since we are in RC that breaking change is still acceptable + I did a quick search on the entire GitHub and it seems no many ppl is using that hook, should be easy to migration as well).

As I don't expect more breaking changes from Shiki, the beta version is used to make sure everything works fine and the migration path is reasonable - It's ok to either have this now, or wait a few days for stable 1.0 release - either way should do the same.

@brc-dd
Copy link
Member

brc-dd commented Jan 27, 2024

Let’s cut another rc and wait for few days before releasing stable.

@brc-dd brc-dd merged commit b8487d3 into main Jan 27, 2024
@brc-dd brc-dd deleted the feat/back-to-shiki branch January 27, 2024 06:02
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants