shikiConfig not applying to Code components outside markdown about astro HOT 6 CLOSED

Can you provide a minimal reproduction? Thank you.

from astro.

@matthewp The issue is very straightforward, just apply some shikiConfig in your astro config and notice it renders in .md but not via the Code component.

I don't know if this is by design or what but there's no ambiguity so creating a minimal repro just feels like a hoop jumping.

If you're genuinely having a problem understanding or reproing the issue I will create one. In the meantime feel free to refer to the astro config I have in the branch I linked and try adding a Code component.

from astro.

Creating a minimal repro is not about proving the bug exists. I believe that it does. The minimal repro helps with debugging and finding the bug. It saves the developer from needing to create one themselves. Thanks.

from astro.

Well I'm creating this bug as a courtesy to the project and community as I've already found a way to work around this issue locally.

As a maintainer myself, I don't think it's fair to expect users to do extra legwork just so I can avoid it, which would imply I value my own time above theirs.

Personally, I'd value the work that went into submitting something like this in the first place and would want to ensure my bugs were known and triaged, but if you want to close the issue, that's your prerogative as a maintainer.

from astro.

Sounds good.

Additionally, after talking with others we have never supported this config being applied outside of Markdown since the config is not serializable at runtime. That's why this config is under markdown and not something like syntaxHighlighting.

from astro.

@matthewp Yeah that's what I wanted to know more about the expected behavior before creating a repro.

I realize it being in the "markdown" key is a little suspicious, but as far as I could tell that was the only config location for it.

I do think it would be very convenient to have some built-in way to get consistent behavior but if it doesn't sound like a feature worth prioritizing I understand.

from astro.