Describe the bug
I am authoring long-form content that does not use an index.md. Instead, the entrypoint .md for a given dir has frontmatter like
...
aliases:
- index
This allows me to have a content/ file structure like
content/
chapters/
chapter-1-name.md <--(this is aliased to index)
chapter-2-name.md
...
main-title-of-content.md <--(this is aliased to index)
other-arbitrary.md
metadata-pages.md
However when using enableSPA: true, links such as the breadcrumbs that point up one or more directories behave incorrectly. In the example above, the "Home" breadcrumb on /chapters/chapter-n-name will result in the browser navigating to /chapters/main-title-of-content instead of /main-title-of-content.
This appears to be because the content of the redirect is fetch'd and then patched into the current page using minimorph without rewriting the url in the meta tag, causing the redirect to be applied relative to the current path instead of the path the alias resides at.
To Reproduce
Steps to reproduce the behavior:
Ensure quartz.config.ts has enableSPA: true
Have a content/ root without index.md
Add a file (e.g. faux-index.md) with frontmatter containing aliases: [index] (or multiline version)
Add a file to a subdirectory (e.g. demo/child-page.md)
Start local server with npx quartz build --serve
Visit the child page in your browser, then click the "Home" breadcrumb
Expected behavior
Quartz navigates to the aliased content at the unnested path.
Describe the bug I am authoring long-form content that does not use an
index.md. Instead, the entrypoint.mdfor a given dir has frontmatter likeThis allows me to have a
content/file structure likeHowever when using
enableSPA: true, links such as the breadcrumbs that point up one or more directories behave incorrectly. In the example above, the "Home" breadcrumb on/chapters/chapter-n-namewill result in the browser navigating to/chapters/main-title-of-contentinstead of/main-title-of-content.This appears to be because the content of the redirect is
fetch'd and then patched into the current page usingminimorphwithout rewriting the url in the meta tag, causing the redirect to be applied relative to the current path instead of the path the alias resides at.To Reproduce Steps to reproduce the behavior:
quartz.config.tshasenableSPA: truecontent/root withoutindex.mdfaux-index.md) with frontmatter containingaliases: [index](or multiline version)demo/child-page.md)npx quartz build --serveExpected behavior Quartz navigates to the aliased content at the unnested path.
Screenshots and Source I have created a minimal reproduction https://github.com/joequincy/quartz-spa-repro/commit/b64659214988e52f35ebcbb46de7e3a314569569 with two pages. Just run
npx quartz build --serveon thereprobranch.Desktop (please complete the following information):
nodeVersion: 20.9.0npmversion: 10.8.1Additional context I have also found what appears to be the source of the issue, and produced a potential fix on my reproduction. https://github.com/joequincy/quartz-spa-repro/commit/36703feb9e2c121945281a4d6b9d3dafa5af8a87 is on a separate
potential-fixbranch for local testing.