Divyansh Singh

> Is `chore/vite3` the branch you're working on? Yeah, [`chore/vite-3`](https://github.com/vuejs/vitepress/tree/chore/vite-3). But that `moduleResolution` thing is not there as I wasn't able to make it work.

Okay, so now there is another issue. VitePress is unable to resolve custom theme if its in TS (and user has not added moduleResolution: nodenext to their tsconfig.json) :/

> Can it be tested easily? ```sh git clone https://github.com/vuejs/vitepress -b chore/vite-3 cd vitepress pnpm i && pnpm build && pnpm pack cd .. mkdir foo cd foo pnpm add...

> I'm not sure why? Probably has something to with our aliases.

Putting Vue-style interpolations in Markdown headings also messes up automatic element IDs (for anchors).

What's the use case?

Ah, you want sidebar items to be on navbar? Any particular UI that you have in mind for this? I guess this can be done at your end using the...

Well there is another workaround. Move your old docs to a subdomain. Then you can write config like this: ```js import { defineConfig } from 'vitepress' export default defineConfig({ themeConfig:...

Hi! Yeah we would fix all these issues. In the meanwhile, you can track #631. Can you help us figure out all such labels to override?

Fixing this is simple, we just need to use `v-html="foo"` instead of `{{ foo }}` syntax in `VPFeature.vue`. But might need to add styles for links to distinguish them: