fix: Remove unnecessary <base> tag causing relative link routing issues #582
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Key Changes
Fixes #495 , #576
This PR removes the
<base>tag injection from thetransformHeadfunction inshared.mtsthat was causing relative links to break in production builds.Problem:
When clicking relative links like
./examples/submit-button.htmlfrom/code-quality/code/, the browser incorrectly navigates to/code-quality/examples/submit-button.htmlinstead of the expected/code-quality/code/examples/submit-button.html.Root Cause:
The HTML
<base>tag forces all relative paths to resolve from/code-quality/, overriding the current page's path. This conflicts with VitePress's client-side routing, which already handles base path configuration correctly.Solution:
Remove the manual
<base>tag injection fromtransformHead. VitePress's built-inbaseconfiguration is sufficient for proper routing without the need for an explicit HTML<base>tag.🖼️ Before and After Comparison