Ben

好鬼劲，俾个 like 俾作者

and the below version has the higher star😄

> * Removed filtering of modifierkey to allow to handle them in ToInputs. > * Filtered triggering of modifier display for modifierkeys themselves in > ToInputs. > * Exposed IsModifierKeyPress...

@ManasMadrecha My solution is adding the custom Remark plugins as a npm module, you can check this [repo](https://github.com/Benbinbin/BlogiNote/blob/2e8b6bcdddbb629c5e81c20ba5f42007d157146c/package.json#L41-L43) for more detail. Refer to this stackoverflow [answer](https://stackoverflow.com/a/38417065/10699431).

@ManasMadrecha yep, you're right

I have created a discussion https://github.com/nuxt/content/discussions/1253 about the MDC syntax, I think the non-invasive way is using the markdown comment syntax like `` as MDC syntax

another suggestion is the VSCode MDC plugin don't provide the intellisense in markdown file, like which prop name the MDC can be set while writing in `*.md` file

maybe you can using the `where` to make it work ```js const queryBuilder = queryContent().where({ _path: { $contains: '/article' } }) const { data: tree } = await useAsyncData('tree', ()...

you should setting the highlight language at `nuxt.config.ts` check this [issue](https://github.com/nuxt/content/issues/1265#issuecomment-1162868259) for more detail this is the [live demo](https://codesandbox.io/s/aged-forest-yjzzw4?file=/nuxt.config.ts)

> Seems quite inconvenient for one-time, project-specific plugins. Is there not a syntax for importing local plugins? @innocenzi maybe the [hook `content:file:afterParse`](https://content.nuxtjs.org/api/advanced#contentfileafterparse) provided by Nuxt Content is [the alternative solution](https://github.com/Benbinbin/BlogiNote/issues/1#issuecomment-1486508025)...