Link Component with or without useBaseUrl

🐛 Bug Report

When using the useBaseUrl hook, the base url is composed dependent on if current page was navigated to through “spa navigation” or visiting the url directly. If one navigates to a url with the “spa” mode, the trailing slash appears to be missing. If you refresh the page, the trailing slash is added. The trailing slash appears to break all of the relative links then.

This could possibly be a misunderstanding with the docs and we are not supposed to be using the hook, but the docs for Link and useBaseUrl do not make it clear when you should use useBaseUrl.

Have you read the Contributing Guidelines on issues?

Yes.

To Reproduce

(gif alt: shows steps as noted above)

Expected behavior

Internal routing to work.

Actual Behavior

It seems to work inconsistently depending on how you have arrived on the page.

Your Environment

• Docusaurus version used: 2.0.0-alpha.55

Reproducible Demo

• Permalink to live url: https://deploy-preview-49--tauri.netlify.app/
• Permalink to code at above url: https://github.com/tauri-apps/tauri-docs/tree/ba99d196f5022807922b3efd0b4330c6e37e4c46

[yangshun]

I think Docusaurus should take a stance on this and introduce trailing slashes to all Docusaurus-generated links while we’re still in alpha. Some users Markdown links might break now but at least it’s consistently breaking in both development and production, unlike now when it’s breaking only in production and sometimes depending on hosting provider.

[jknoxville]

So either you use a trailing slash for all your internal links, or use absolute links.

As a user, always using a trailing slash doesn’t currently seem to be an option. The navbar sidebar sends you to pages without trailing slashes. Then refreshing that page adds a trailing slash.

As far as I can tell, this means all relative URLs are broken depending on how you use the website. IMO we should issue a fix for this soon or make it clearer that they don’t work, maybe by throwing an error at build time or something like that.

The docs are still implying relative URLs should be ok: https://v2.docusaurus.io/docs/markdown-features#referencing-other-documents

Also, even when specifying a relative url in a markdown file, the resultant a-tag on the page has an absolute href, so I don’t think the browser’s behaviour is the problem here, the wrong absolute path seems to be being produced by docusaurus itself.