[0.27]: Seems like Shiki languages have changed; bash & console no longer valid.

[typhonrt]

It seems like shiki was updated for 0.27 and bash and console are no longer supported languages.

While it seems like they are still listed in the default configuration internally in Typedoc if copying the default array as seen in Typedoc docs and setting this to highlightLanguages option this will trigger an error in the option validator.

Ahh... I can see this being a consequence of your rebundling of shiki @gerrit0/mini-shiki

If bash and console are no longer valid; easy suggestion is to remove them from Typedoc docs and internal default.

Environment

• Typedoc version: 0.27.2

[Gerrit0]

This shouldn't have changed, mini-shiki is meant to be a complete drop in replacement.

[typhonrt]

This is when using the same exact default options IE:

{
    "highlightLanguages": [
        "bash",
        "console",
        "css",
        "html",
        "javascript",
        "json",
        "jsonc",
        "json5",
        "tsx",
        "typescript"
    ]
}

With bash / console:

Without bash & console docs generate fine:

---

Despite the error docs generate, but seemingly falls back to the internal default. I just happen to be adding svelte to the languages. This does work sans bash & console, however with them added the error message posts and the Svelte code block is not transformed.

[Gerrit0]

If you were using TypeDoc's CLI, it would have exited without generating docs due to the configuration error. Options aren't set if they fail validation.

I'm not sure why I decided to only allow non-aliased languages when implementing this ages ago, I experimentally just allowed it and it all works as expected.... makes it an easy default.

[typhonrt]

Yeah this is programmatic usage / special case / complex docs project.