Symbolic linked `srcDir` makes redirects

[ryansuhartanto]

Describe the bug

I set up my monorepo structure into this using ln -s ../../docs .:

docs/
apps/docs/
├── docs -> ../../docs
└── .vitepress

I plan to docs is managed outside of the VitePress project and configured my .vitepress/config.ts into this:

export default defineConfig({
  srcDir: "docs",
  // ...
});

But running vitepress dev would redirects the site into http://localhost:5173/docs.

Reproduction

Checkout this for a similar issue: https://stackblitz.com/edit/vitepress-symlink.

Expected behavior

Should not redirect from http://localhost:5173/ to http://localhost:5173/docs.

System Info

From the Stackblitz:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm

Additional context

No response

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

Hmm, it's not redirecting but it's changing the history for some reason.

As a workaround, you can just change the srcDir instead of symlinking - https://stackblitz.com/edit/vitepress-symlink-ravxn19n?file=packages/docs/.vitepress/config.ts,.stackblitzrc,packages/docs/package.json

[ryansuhartanto]

Can you check again?

I used the "Open preview in new tab", the url is definitely keep redirecting to /docs/.

The url in my end looks something like this:

https://vitepresssymlink-dxr3--5173--96435430.local-credentialless.webcontainer.io/docs/

[brc-dd]

You are probably opening different stackblitz, the link is like this for me:

I think you're opening the original one. Can you check the one I shared above?

[ryansuhartanto]

The one you shared one works nicely, I guess I'll just do the workaround for now.