Skip to content

fix(search): use absolute bundle-path for Pagefind Component UI #1021

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.

Sign up for GitHub

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

Merged
DeepDiver1975 merged 1 commit into from
Jun 16, 2026
Merged

fix(search): use absolute bundle-path for Pagefind Component UI #1021

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions src/partials/header-content.hbs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,12 @@
<span class="navbar-title">{{site.title}}</span>
</a>
<div class="navbar-item search">
{{!-- Pagefind Component UI modal search. pagefind-config points the
components at the index emitted by `pagefind --site` under
siteRootPath; the trigger button opens the modal overlay (also
via the Ctrl/Cmd+K shortcut). --}}
<pagefind-config bundle-path="{{{siteRootPath}}}/pagefind/"></pagefind-config>
{{!-- Pagefind Component UI modal search. The trigger opens the modal
overlay (also via Ctrl/Cmd+K). bundle-path MUST be absolute/root-
relative: the components dynamic-import() pagefind.js relative to
pagefind-component-ui.js's URL, so a page-relative "./pagefind/"
(siteRootPath on shallow pages) doubles to /pagefind/pagefind/. --}}
<pagefind-config bundle-path="/pagefind/"></pagefind-config>
<pagefind-modal-trigger></pagefind-modal-trigger>
<pagefind-modal reset-on-close></pagefind-modal>
</div>
Expand Down