You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even whilst running the app in production mode locally, it builds the search index as I expect it to, and then the search functionality itself works as I expect it to.
However, when deploying onto Vercel - according to the build logs - it builds the search index correctly, however when searching for the same content as I did locally it returns no results.
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Home
Available memory (MB): 16307
Available CPU cores: 16
Binaries:
Node: 22.2.0
npm: 10.7.0
Yarn: N/A
pnpm: 9.2.0
Relevant Packages:
next: 14.2.4 // Latest available version is detected (14.2.4).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: 5.4.5
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Core, MDX
Additional context
I have altered the setup to remove /docs being the root, and instead / being the root, as for our use case the docs would be hosted as a separate website to the main website. Albeit unlikely, maybe this has broken something?
The text was updated successfully, but these errors were encountered:
Don't use that example in production, it's not compatible with serverless runtime. It's just for experimental purposes. As we recommended, use 3rd party solutions like Algolia Search.
Otherwise, using the Fumadocs built-in search, it requires a redeployment when your content changes, which wasted the optimisation of MDX remote.
To Reproduce
Current vs. Expected behavior
Even whilst running the app in production mode locally, it builds the search index as I expect it to, and then the search functionality itself works as I expect it to.
However, when deploying onto Vercel - according to the build logs - it builds the search index correctly, however when searching for the same content as I did locally it returns no results.
Provide environment information
Which area(s) are affected? (Select all that apply)
Core, MDX
Additional context
I have altered the setup to remove
/docs
being the root, and instead/
being the root, as for our use case the docs would be hosted as a separate website to the main website. Albeit unlikely, maybe this has broken something?The text was updated successfully, but these errors were encountered: