Describe the bug
I upgraded @orama/plugin-docusaurus-v3 on my project from v3.1.1 to v.3.1.18, and my search results got messed up. I had it configured to show the page title and the section's contents with highlighting enabled, but once I upgraded the plugin my search results would only display the section's contents and no highlighting.
To Reproduce
I created a minimal example here: https://github.com/Lucioschenkel/docusaurus-orama-example.
HEAD is with @orama/plugin-docusaurus-v3 at v3.1.18, HEAD~1 is a working example using the same config, and @orama/plugin-docusaurus-v3 at 3.1.1.
Expected behavior
Since this was a patch version update, I didn't expect breaking changes the the API. I also couldn't find any documentation on how the components should behave. The links to the SearchBox and SearchButton components docs are broken: https://docs.orama.com/docs/orama-js/plugins/plugin-docusaurus
Environment Info
OS: Mac 26.2
Node: v24.11.1
Docusaurus: 3.9.1
`@orama/plugin-docusaurus-v3`: `3.1.18`
Affected areas
Search
Additional context
Non-working example:
Working example (using v3.1.1):

Describe the bug
I upgraded
@orama/plugin-docusaurus-v3on my project fromv3.1.1tov.3.1.18, and my search results got messed up. I had it configured to show the page title and the section's contents with highlighting enabled, but once I upgraded the plugin my search results would only display the section's contents and no highlighting.To Reproduce
I created a minimal example here: https://github.com/Lucioschenkel/docusaurus-orama-example.
HEAD is with
@orama/plugin-docusaurus-v3atv3.1.18, HEAD~1 is a working example using the same config, and@orama/plugin-docusaurus-v3at3.1.1.Expected behavior
Since this was a patch version update, I didn't expect breaking changes the the API. I also couldn't find any documentation on how the components should behave. The links to the
SearchBoxandSearchButtoncomponents docs are broken: https://docs.orama.com/docs/orama-js/plugins/plugin-docusaurusEnvironment Info
Affected areas
Search
Additional context
Non-working example:
Working example (using
v3.1.1):