Repository navigation
Search is broken for certain articles #8337
Description
Activity
good report - thanks for this.
we do have some plans to change learn content as a result of nodejs/learn#40 or #8272 - but we should resolve this in production too.@micheleriva is this anything on your end that we should be aware of?
Reacted by Efe KarasakalHi @bmuenzenmeyer, @efekrskl we have a PR open (#8175) that moves the whole search infra to the new Orama Cloud. Can you please test if here it is working as expected? Node.js is currently on an old infra (with an old version of Orama) and all the fixes will be deployed in the new one - except, of course, if search is severely broken!
In this report it looks like the problem is with syncing data rather than accessing it. This should also be solved in #8175, which should be ready to be merged per the last comments (@ovflowd)
Yes, this issue still persists in the Preview of #8175
As mentioned in the issue body, this is somehow related to the filenames. I didn't have time to do a deep dive though
Oh Gosh you're right sorry - I misinterpreted the issue when I first read it. It does look like the problem is with file names - especially with
index.mdones. Should be an easy fix though. Let me check this in #8175.Reacted by Efe Karasakal- added a parent issue
on Nov 7, 2025 This issue is resolved
URL:
https://nodejs.org/en
Browser Name:
Chrome
Browser Version:
141.0.7390.123
Operating System:
macOS Sequoia
How to reproduce the issue:
Start typing...)Memory(as in the Memory article https://nodejs.org/en/learn/diagnostics/memory)https://nodejs.org/en/learn/diagnostics/memory/index#memoryIt looks like this is because these articles are named as
index.mdinstead of an actual slug. This means:live-debuggingpoor-performancememoryshould have the same bug