`MiniSearch: duplicate ID` error when restarting the dev server (Duplicate for #4251)

[Teraskull]

Describe the bug

Hi,

Opening a duplicate issue here as the original one is locked.
 
Are there any plans for issue #4251? It got automatically closed by the bot but is still an annoying problem.

While the PR in that issue won't handle replacing headers because their anchor id would change, it is still helpful not having to reload the server manually each time after incremental markdown changes when testing the search functionality.

Thanks!

Reproduction

N/A

Expected behavior

N/A

System Info

N/A

Additional context

No response

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

Feel free to recreate that PR. It got closed because the original author deleted their account.

it is still helpful not having to reload the server manually each time after incremental markdown changes when testing the search functionality

Can you share the case where this happens? I think it shouldn't be needed for markdown changes. In original issue, they were using vite's server.restart inside custom plugin that was causing the issue.

[Teraskull]

Basically, if I do a lot of small changes in a markdown segment, like rewriting/rewording, and want to preview how it looks when searching for the segment, the id of the segment already exists in the cache, so Minisearch throws an error about a duplicate id.

Having the server reload automatically on these changes allows to rebuild the search cache and display fresh changes in the search details.

It's not a big change, this is the whole code from the PR:

if (index.has(id)) {
    index.discard(id)
}

I know this is a very minor issue and more of a nitpick, but sometimes I need to test if it's intuitive enough for my users to find a section by keywords, without having to manually restart docs:dev after every change for the search cache to get refreshed.

Unless there is a better way of course, thanks!

[brc-dd]

I've to do some refactors for the search plugin. I'll fix this there itself. The search index should be partially rebuilt on md changes. For now, I'd say bear with the issue for some more time. Also, you don't need to manually re-run docs:dev, you can just press r in terminal.