fix: use Shiki's `isSpecialLang` to allow `ansi` codeblocks (#10540)

* fix: use `isSpecialLang` instead of hardcode

Hardcoding this value makes it impossible to use Shiki's `ansi` feature

* Add changeset

1 files changed, 2 insertions, 2 deletions

diff --git a/packages/markdown/remark/src/shiki.ts b/packages/markdown/remark/src/shiki.ts
index ff1589dac..fc35c6e92 100644
--- a/packages/markdown/remark/src/shiki.ts
+++ b/packages/markdown/remark/src/shiki.ts
@@ -1,5 +1,5 @@
 import type { Properties } from 'hast';
-import { bundledLanguages, createCssVariablesTheme, getHighlighter } from 'shiki';
+import { bundledLanguages, createCssVariablesTheme, getHighlighter, isSpecialLang } from 'shiki';
 import { visit } from 'unist-util-visit';
 import type { ShikiConfig } from './types.js';
 
@@ -51,7 +51,7 @@ export async function createShikiHighlighter({
 
 	return {
 		highlight(code, lang = 'plaintext', options) {
-			if (lang !== 'plaintext' && !loadedLanguages.includes(lang)) {
+			if (!isSpecialLang(lang) && !loadedLanguages.includes(lang)) {
 				// eslint-disable-next-line no-console
 				console.warn(`[Shiki] The language "${lang}" doesn't exist, falling back to "plaintext".`);
 				lang = 'plaintext';