Question 1

How do I implement fuzzy search with MiniSearch?

Accepted Answer

Set the 'fuzzy' option to a value like 0.2 for edit distance proportional to term length, allowing misspelled queries to match documents, as shown in the search options example.

Question 2

MiniSearch vs Lunr.js: which is better for client-side search?

Accepted Answer

MiniSearch is lighter with zero dependencies and faster for simple use cases, while Lunr.js offers more built-in features like stemming. Choose MiniSearch for minimal footprint or Lunr for richer defaults.

Question 3

Can MiniSearch handle nested fields in documents?

Accepted Answer

Yes, use the 'extractField' option to access nested paths (e.g., 'author.name') or custom logic, as demonstrated in the field extraction example for non-string values.

Question 4

How to save and load a MiniSearch index for persistence?

Accepted Answer

Serialize the index with JSON.stringify on the MiniSearch instance and restore it later, but this requires manual state management since no built-in persistence exists.

Question 5

Does MiniSearch remove stop words automatically?

Accepted Answer

No, but you can filter stop words via the 'processTerm' option by returning null for unwanted terms, as illustrated in the term processing section.

Question 6

What's the performance impact on mobile browsers?

Accepted Answer

Designed for memory-constrained environments, it performs well, but keep index size small to avoid high memory usage, as noted in the resource-efficient feature.

minisearch

What is minisearch?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions