Divyansh Singh

Relative paths should work too unless you are dynamically setting the src prop. Can you share some kind of repository where you are experiencing the issues?

`src="./Note1-fig/Fig1.png"` should also work I guess 👀

Do you need it to work for the top-level item too? Like say if we have something like this: Then do you want the link on "Guide" too? Or just...

Please show the relevant code. Try running locally with vitepress build and vitepress preview. You can set `DEBUG='*'` env variable to get more details.

> Should I set into my production environment No. If everything is fine locally in build and preview, then it's routing issue. Check if your server is serving wrong page...

> And find out minified html Can you show a screenshot showing that view-source output?

I don't think that is the right page? It doesn't have any HTML corresponding to home page. It is a routing issue. It's probably serving some fallback or something. Check...

No. `view-source:https://foo.bar/` shows what your server is sending. It doesn't execute any JS.

You can use this plugin - https://github.com/fabioaanthony/markdown-it-vuepress-code-snippet-enhanced example: ```ts // #foo import { defineConfig } from 'vitepress' import snippetPlugin from 'markdown-it-vuepress-code-snippet-enhanced' // #foo export default defineConfig({ markdown: { // #foo...

This is fixed in Node 22, which now shows path argument when any fs call fails. Also, the newer versions of vitepress show the file where the bundling failed: