Divyansh Singh

The solution in #2581 seems to work for most cases, but one might also need to add some plugin like https://github.com/ElMassimo/vite-plugin-full-reload e.g. in cases where a vue component is both...

Okay, so this should work fine without any extra config in next version. I went with a slightly modified approach of what I had earlier proposed in 7dbceaa

Not possible to do it using config as functions are not serializable (x-ref https://github.com/vuejs/vitepress/issues/1381#issuecomment-1337162977). Manually create an Algolia component and register it in on of the navbar slots.

Let's just document the alias method. I don't think there is any other way to properly replace the theme components.

Let's track #2699 here itself.

Outline is now generated purely on client-side. So if one specifies `id` on heading elements, it will show up on the outline. > Probably will have to add some custom...

@ryan4yin Yeah now there are multiple hooks that can add head tags based on the page. So you can have site level head tags + page level tags (say for...

@ryan4yin Do something like this: ```ts import { defineConfig } from 'vitepress'; export default defineConfig({ transformPageData(pageData) { return { frontmatter: { ...pageData.frontmatter, head: [ [ 'script', { type: 'application/ld+json' },...

Yeah I think we can support that. I'll take a look.

Versioning isn't supported. There might be some hacky workarounds, but it'd need some changes at VitePress level.