Use shikiji

[bluwy]

Changes

Use shikiji instead of shiki. Also added compat code so it should work as before

Testing

Existing tests should pass

Docs

Most docs around shiki should also apply to shikiji, so I don't think we need to update the docs. The ideal case is to also have shikiji's improvements upstreamed to shiki.

[changeset-bot]

🦋 Changeset detected

Latest commit: b491e6b

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

This PR is blocked because it contains a minor changeset. A reviewer will merge this at the next release if approved.

[ematipico]

It looks good to me. I wonder if we could move shared code inside the internal-helpers package.

[sarah11918]

With respect to docs, I would only expect we need to add docs to the site if:

• someone upgrades to 3.3 and suddenly their site looks different, without doing anything (this would be a breaking change, and should be in the changeset)
• someone has additional config options, or more options to existing config values, that they can set
• there is something new they can do now that they couldn't before (or the opposite, some behaviour has been removed)
• there is a different way to do something that they could previously do

Outside of these conditions, there's probably not much we would document? We don't tend to explain a lot of inner workings, but rather how to do things. If the user has to act differently, or will notice different behaviour even as the result of changing nothing, these are the two big flags for docs.

[bluwy]

@sarah11918

1. The site should look the same. The themes are copied from shiki from shikiji.
2. The existing options stay the same. shikiji does have extra APIs, but it's not exposed to the user yet.
3. For now there's no new or removed features.
4. Existing patterns stay the same.

Probably the only visible change is the markup where style="color: #ffffff" is now style="color:#ffffff".

And <span class="line" style="color: #ffffff" is now <span class="line" + <code class="astro-code" style="color:#ffffff". It's a new strategy where span.line inherits the color from code instead. Maybe I can document this in the changeset, but I'm not really sure if it'll affect people a lot.

[sarah11918]

Looks great, @bluwy ! Just some very minor changes to the opening line, but I think this is more than helpful for describing the change!

merge day