Open dusanbobicic opened 3 weeks ago
@dusanbobicic hopefully a fix gets pushed soon, but I got it to work with npm run swizzle.
I was able to get orama working with docusaurus 3.4.0, by using npm swizzle and ejecting: and then i updated @orama/searchbox, and then setting @orama/searchbox in my package.json to an older version at 1.0.0-rc33
Describe the bug
First we tried integrating the OSS version of the plugin on the existing solution instead of lunr search plugin but we got an error. To verify that the issue is with the orama plugin we've tried on a fresh docusaurus project and it did not work. We are getting some react errors. See the image below:![image](https://github.com/askorama/orama/assets/9326334/2340f3a9-79e1-4710-94e3-cba5d05d3e6e)
Error link
When we run the website in development mode using:
npm run start
We get a following error which describes more the minified issue:Thanks for taking your time!
To Reproduce
npm run build
npm run serve
Expected behavior
Site is built and docusaurus website is rendered with search box.
Environment Info
Affected areas
Initialization, Search
Additional context
No response