Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch language error when build with a base path #103

Closed
dewfall123 opened this issue Oct 23, 2020 · 1 comment · Fixed by #104
Closed

Switch language error when build with a base path #103

dewfall123 opened this issue Oct 23, 2020 · 1 comment · Fixed by #104
Labels
bug Something isn't working

Comments

@dewfall123
Copy link
Contributor

Describe the bug
Switch language error when build with a base path

To Reproduce
Steps to reproduce the behavior:

  1. clone https://github.com/dewfall123/vitepress-issues
  2. run
    yarn
    yarn build
    yarn build-dev
  3. open http://127.0.0.1:3001 and switch language several times.
    It go to error path like http://127.0.0.1:3001/vhooks/vhooks/zh/index.html.

Expected behavior
Switch language and go to the correct path.

System Info

  • vitepress version: 0.7.0
  • vite version: v1.0.0-rc.4
  • Node version: 14
  • OS version: window 10
@dewfall123 dewfall123 added the bug: pending triage Maybe a bug, waiting for confirmation label Oct 23, 2020
@kiaking kiaking added bug Something isn't working and removed bug: pending triage Maybe a bug, waiting for confirmation labels Oct 23, 2020
@kiaking
Copy link
Member

kiaking commented Oct 23, 2020

Confirmed this is a bug. We should fix it.

kiaking added a commit that referenced this issue Oct 29, 2020
fix #103
fix #106

Co-authored-by: zuofenghua <11100776@bbktel.com>
Co-authored-by: Kia Ishii <kia.king.08@gmail.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants