elasticlunr vs flexsearch vs fuse.js vs minisearch
Client-Side Full-Text Search Libraries for JavaScript
elasticlunrflexsearchfuse.jsminisearchSimilar Packages:

Client-Side Full-Text Search Libraries for JavaScript

elasticlunr, flexsearch, fuse.js, and minisearch are JavaScript libraries designed to enable search functionality directly within the browser or Node.js environment without needing a backend search server. They allow developers to index data locally and perform queries instantly. fuse.js specializes in fuzzy matching for typo tolerance, while flexsearch focuses on extreme speed and concurrency. minisearch offers a balanced, modern API with field boosting, and elasticlunr is a legacy fork of lunr.js that is no longer maintained.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
elasticlunr02,069-7710 years agoMIT
flexsearch013,6972.33 MB308 months agoApache-2.0
fuse.js020,245312 kB3a month agoApache-2.0
minisearch05,950827 kB108 months agoMIT

Client-Side Full-Text Search Libraries for JavaScript

When building web applications, you often need to let users search through data without hitting a backend server every time. Libraries like elasticlunr, flexsearch, fuse.js, and minisearch solve this by indexing data in the browser. However, they differ significantly in speed, accuracy, and maintenance status. Let's break down how they handle real-world engineering challenges.

๐Ÿ—๏ธ Setup and Indexing: How Data Is Stored

The way you feed data into these libraries dictates how you structure your application state.

elasticlunr requires a pipeline similar to its parent lunr.js. You define fields and add documents one by one or in bulk.

// elasticlunr: Define index and add docs
var idx = elasticlunr(function () {
  this.addField('title');
  this.addField('body');
  this.setRef('id');
});

idx.add({ id: 1, title: 'React Guide', body: '...' });

flexsearch uses a more granular approach. You often create separate indexes for different fields to optimize speed, or use a document index for structured data.

// flexsearch: Document index setup
const index = new FlexSearch.Document({
  document: {
    id: "id",
    index: ["title", "body"]
  }
});

index.add({ id: 1, title: 'React Guide', body: '...' });

fuse.js does not require a separate indexing step. You pass the array of data directly to the search instance, which builds the index internally upon initialization.

// fuse.js: Initialize with data array
const list = [{ id: 1, title: 'React Guide', body: '...' }];
const fuse = new Fuse(list, {
  keys: ['title', 'body']
});

minisearch requires explicit index creation before adding documents, similar to elasticlunr but with a more modern promise-based API.

// minisearch: Define fields and add docs
const miniSearch = new MiniSearch({
  fields: ['title', 'body'],
  storeFields: ['title']
});

miniSearch.addAll([{ id: 1, title: 'React Guide', body: '...' }]);

๐Ÿ” Search Capabilities: Fuzzy vs. Exact Matching

Not all search is the same. Sometimes you need exact matches; other times you need to forgive typos.

elasticlunr supports basic token matching and boosting but lacks advanced fuzzy logic out of the box without plugins.

// elasticlunr: Basic query with boost
var results = idx.search('react guide', { fields: { title: { boost: 2 } } });

flexsearch supports prefix search and context matching. Fuzzy search is available but requires specific configuration flags.

// flexsearch: Query with prefix and limit
const results = index.search('react', {
  query: 'react',
  limit: 10,
  suggest: true // Enables typo tolerance
});

fuse.js is the industry standard for fuzzy search. It uses a distance algorithm to find matches even with misspellings.

// fuse.js: Search with threshold for fuzziness
const results = fuse.search('reacct', {
  limit: 10
});
// Returns matches despite typo 'reacct' vs 'react'

minisearch supports fuzzy search via a fuzzy option in the search call, balancing speed and accuracy.

// minisearch: Search with fuzzy option
const results = miniSearch.search('reacct', {
  fuzzy: 0.2, // Tolerance level
  boost: { title: 2 }
});

โšก Performance and Concurrency

Speed matters when your dataset grows beyond a few hundred items.

elasticlunr is synchronous and blocks the main thread. It is not suitable for large datasets on the UI thread.

// elasticlunr: Synchronous search (blocks thread)
var results = idx.search('query');
// No built-in concurrency support

flexsearch is designed for speed. It supports web workers and concurrent indexing to keep the UI responsive.

// flexsearch: Async search to avoid blocking
index.searchAsync('query').then(results => {
  console.log(results);
});

fuse.js is generally slower than flexsearch on large datasets because of the fuzzy matching overhead. It runs synchronously by default.

// fuse.js: Synchronous search
const results = fuse.search('query');
// Can cause lag with 10k+ items

minisearch is optimized for performance but runs synchronously. It is faster than fuse.js for exact matches but slower than flexsearch.

// minisearch: Synchronous search
const results = miniSearch.search('query');
// Lightweight enough for most UI threads

๐Ÿ› ๏ธ Maintenance and Ecosystem Health

Choosing a library is also about choosing a maintainer. You do not want to inherit technical debt.

elasticlunr is deprecated. The repository has not seen significant updates in years. Using it introduces security risks and compatibility issues with modern build tools.

// elasticlunr: No modern TypeScript types or ES module support
// import elasticlunr from 'elasticlunr'; // Often requires legacy bundler config

flexsearch is actively maintained by a single dedicated developer. It is stable but has a unique API that changes occasionally between major versions.

// flexsearch: ES Module support
import FlexSearch from 'flexsearch';

fuse.js is widely adopted and stable. It has excellent TypeScript support and is a safe bet for long-term projects.

// fuse.js: Robust TypeScript definitions
import Fuse from 'fuse.js';

minisearch is modern, open-source, and actively maintained. It is built with ES modules in mind and integrates well with modern frameworks like React and Vue.

// minisearch: Modern ES Module usage
import MiniSearch from 'minisearch';

๐ŸŒฑ When Not to Use These

These libraries are for client-side use. Avoid them when:

  • You need to search millions of records. Use a backend service like Elasticsearch or Algolia instead.
  • You need real-time collaboration search. Backend indexing is required for multi-user consistency.
  • Your data is highly sensitive. Client-side search exposes the entire dataset to the user's browser.

๐Ÿ“Œ Summary Table

Featureelasticlunrflexsearchfuse.jsminisearch
StatusโŒ Deprecatedโœ… Activeโœ… Activeโœ… Active
Primary StrengthLegacy CompatibilityRaw SpeedFuzzy MatchingBalanced DX
IndexingManual PipelineDocument/FieldAutomaticManual Pipeline
Fuzzy SearchLimitedConfigurableExcellentGood
Async SupportNoYesNoNo

๐Ÿ’ก Final Recommendation

Think in terms of data size and user behavior:

  • Need typo tolerance? โ†’ Go with fuse.js. It handles misspellings better than the rest.
  • Need maximum speed? โ†’ Go with flexsearch. It is the fastest option for large datasets.
  • Need a modern standard? โ†’ Go with minisearch. It offers the best balance of features, maintenance, and ease of use.
  • Never start new work with elasticlunr. It is obsolete.

Final Thought: All four libraries solve the same problem, but flexsearch, fuse.js, and minisearch represent the modern standard. Choose based on whether speed or fuzzy matching matters more for your users.

How to Choose: elasticlunr vs flexsearch vs fuse.js vs minisearch

  • elasticlunr:

    Avoid elasticlunr for any new project. It is deprecated and has not received updates in years, posing security and compatibility risks. If you have a legacy system using it, plan a migration to minisearch or flexsearch immediately.

  • flexsearch:

    Choose flexsearch when raw performance is your top priority and you are dealing with large datasets (100k+ documents). It is ideal for complex search scenarios requiring context mapping or high concurrency, but be prepared for a steeper learning curve due to its verbose API.

  • fuse.js:

    Choose fuse.js if your primary requirement is fuzzy search with high typo tolerance. It is the best fit for search bars where users might misspell terms, such as contact lists or product catalogs with inconsistent naming, though it is slower on very large datasets.

  • minisearch:

    Choose minisearch for a modern, well-maintained balance between speed and features. It is perfect for most standard UI search needs, offering field boosting, filtering, and a clean API without the complexity of flexsearch or the abandonment risk of elasticlunr.

README for elasticlunr

Elasticlunr.js

Build Status npm version GitHub license

Elasticlunr.js is a lightweight full-text search engine developed in JavaScript for browser search and offline search. Elasticlunr.js is developed based on Lunr.js, but more flexible than lunr.js. Elasticlunr.js provides Query-Time boosting, field search, more rational scoring/ranking methodology, fast computation speed and so on. Elasticlunr.js is a bit like Solr, but much smaller and not as bright, but also provide flexible configuration, query-time boosting, field search and other features.

Why You Need Lightweight Offline Search?

  1. In some system, you don't want to deploy any complex full-text search engine(such as Lucence, Elasticsearch, Sphinx, etc.), you only want to provide some static web pages and provide search functionality , then you could build index in previous and load index in client side(such as Browser).
  2. Provide offline search functionality. For some documents, user usually download these documents, you could build index and put index in the documents package, then provide offline search functionality.
  3. For some limited or restricted network, such WAN or LAN, offline search is a better choice.
  4. For mobile device, Iphone or Android phone, network traffic maybe very expensive, then provide offline search is a good choice.
  5. If you want to provide search functionality in your Node.js system, and you don't want to use a complex system, or you only need to support thousands of documents, then Elasticlunr.js is what you want to use.

Key Features Comparing with Lunr.js

  1. Query-Time Boosting, you don't need to setup boosting weight in index building procedure, Query-Time Boosting make it more flexible that you could try different boosting scheme.
  2. More Rational Scoring Mechanism, Elasticlunr.js use quite the same scoring mechanism as Elasticsearch, and also this scoring mechanism is used by lucene.
  3. Field-Search, you could choose which field to index and which field to search.
  4. Boolean Model, you could set which field to search and the boolean model for each query token, such as "OR", "AND".
  5. Combined Boolean Model, TF/IDF Model and the Vector Space Model, make the results ranking more reliable.
  6. Fast, Elasticlunr.js removed TokenCorpus and Vector from lunr.js, by using combined model there is no need to compute the vector of a document and query string to compute similarity of query and matched document, this improve the search speed significantly.
  7. Small Index Size, Elasticlunr.js did not store TokenCorpus because there is no need to compute query vector and document vector, then the index file is small, and also user could choose if they need to store the origianl JSON doc, if user care more about the index size, they could choose not store the original JSON doc, this could reduce the index size significantly. This is especially helpful when elasticlunr.js is used as offline search. The index size is about half size of lunr.js index file.

Example

A very simple search index can be created using the following scripts:

var index = elasticlunr(function () {
    this.addField('title');
    this.addField('body');
    this.setRef('id');
});

Adding documents to the index is as simple as:

var doc1 = {
    "id": 1,
    "title": "Oracle released its latest database Oracle 12g",
    "body": "Yestaday Oracle has released its new database Oracle 12g, this would make more money for this company and lead to a nice profit report of annual year."
}

var doc2 = {
    "id": 2,
    "title": "Oracle released its profit report of 2015",
    "body": "As expected, Oracle released its profit report of 2015, during the good sales of database and hardware, Oracle's profit of 2015 reached 12.5 Billion."
}

index.addDoc(doc1);
index.addDoc(doc2);

Then searching is as simple:

index.search("Oracle database profit");

Also, you could do query-time boosting by passing in a configuration.

index.search("Oracle database profit", {
    fields: {
        title: {boost: 2},
        body: {boost: 1}
    }
});

This returns a list of matching documents with a score of how closely they match the search query:

[{
    "ref": 1,
    "score": 0.5376053707962494
},
{
    "ref": 2,
    "score": 0.5237481076838757
}]

If user do not want to store the original JSON documents, they could use the following setting:

var index = elasticlunr(function () {
    this.addField('title');
    this.addField('body');
    this.setRef('id');
    this.saveDocument(false);
});

Then elasticlunr.js will not store the JSON documents, this will reduce the index size, but also bring some inconvenience such as update a document or delete a document by document id or reference. Actually most of the time user will not udpate or delete a document from index.

API documentation is available, as well as a full working example.

Description

Elasticlunr.js is developed based on Lunr.js, but more flexible than lunr.js. Elasticlunr.js provides Query-Time Boosting, Field Search, more rational scoring/ranking methodology, flexible configuration and so on. A bit like Solr, but much smaller and not as bright, but also provide flexible configuration, query-time boosting, field search, etc.

Installation

Simply include the elasticlunr.js source file in the page that you want to use it. Elasticlunr.js is supported in all modern browsers.

Browsers that do not support ES5 will require a JavaScript shim for Elasticlunr.js to work. You can either use Augment.js, ES5-Shim or any library that patches old browsers to provide an ES5 compatible JavaScript environment.

Documentation

This part only contain important apects of elasticlunr.js, for the whole documentation, please go to API documentation.

1. Build Index

When you first create a index instance, you need to specify which field you want to index. If you did not specify which field to index, then no field will be searchable for your documents. You could specify fields by:

var index = elasticlunr(function () {
    this.addField('title');
    this.addField('body');
    this.setRef('id');
});

You could also set the document reference by this.setRef('id'), if you did not set document ref, elasticlunr.js will use 'id' as default.

You could do the above index setup as followings:

var index = elasticlunr();
index.addField('title');
index.addField('body');
index.setRef('id');

Also you could choose not store the original JSON document to reduce the index size by:

var index = elasticlunr();
index.addField('title');
index.addField('body');
index.setRef('id');
index.saveDocument(false);

2. Add document to index

Add document to index is very simple, just prepare you document in JSON format, then add it to index.

var doc1 = {
    "id": 1,
    "title": "Oracle released its latest database Oracle 12g",
    "body": "Yestaday Oracle has released its new database Oracle 12g, this would make more money for this company and lead to a nice profit report of annual year."
}

var doc2 = {
    "id": 2,
    "title": "Oracle released its profit report of 2015",
    "body": "As expected, Oracle released its profit report of 2015, during the good sales of database and hardware, Oracle's profit of 2015 reached 12.5 Billion."
}

index.addDoc(doc1);
index.addDoc(doc2);

If your JSON document contains field that not configured in index, then that field will not be indexed, which means that field is not searchable.

3. Remove document from index

Elasticlunr.js support remove a document from index, just provide JSON document to elasticlunr.Index.prototype.removeDoc() function.

For example:

var doc = {
    "id": 1,
    "title": "Oracle released its latest database Oracle 12g",
    "body": "Yestaday Oracle has released its new database Oracle 12g, this would make more money for this company and lead to a nice profit report of annual year."
}

index.removeDoc(doc);

Remove a document will remove each token of that document's each field from field-specified inverted index.

4. Update a document in index

Elasticlunr.js support update a document in index, just provide JSON document to elasticlunr.Index.prototype.update() function.

For example:

var doc = {
    "id": 1,
    "title": "Oracle released its latest database Oracle 12g",
    "body": "Yestaday Oracle has released its new database Oracle 12g, this would make more money for this company and lead to a nice profit report of annual year."
}

index.update(doc);

5. Query from Index

Elasticlunr.js provides flexible query configuration, supports query-time boosting and Boolean logic setting. You could setup a configuration tell elasticlunr.js how to do query-time boosting, which field to search in, how to do the boolean logic. Or you could just use it by simply provide a query string, this will aslo works perfectly because the scoring mechanism is very efficient.

5.1 Simple Query

Because elasticlunr.js has a very perfect scoring mechanism, so for most of your requirement, simple search would be easy to meet your requirement.

index.search("Oracle database profit");

Output is a results array, each element of results array is an Object contain a ref field and a score field. ref is the document reference. score is the similarity measurement.

Results array is sorted descent by score.

5.2 Configuration Query

5.2.1 Query-Time Boosting

Setup which fields to search in by passing in a JSON configuration, and setup boosting for each search field. If you setup this configuration, then elasticlunr.js will only search the query string in the specified fields with boosting weight.

The scoring mechanism used in elasticlunr.js is very complex, please goto details for more information.

index.search("Oracle database profit", {
    fields: {
        title: {boost: 2},
        body: {boost: 1}
    }
});

5.2.2 Boolean Model

Elasticlunr.js also support boolean logic setting, if no boolean logic is setted, elasticlunr.js use "OR" logic defaulty. By "OR" default logic, elasticlunr.js could reach a high Recall.

index.search("Oracle database profit", {
    fields: {
        title: {boost: 2},
        body: {boost: 1}
    },
    bool: "OR"
});

Boolean model could be setted by global level such as the above setting or it could be setted by field level, if both global and field level contains a "bool" setting, field level setting will overwrite the global setting.

index.search("Oracle database profit", {
    fields: {
        title: {boost: 2, bool: "AND"},
        body: {boost: 1}
    },
    bool: "OR"
});

The above setting will search title field by AND model and other fields by "OR" model. Currently if you search in multiply fields, resutls from each field will be merged together to give the query results. In the future elasticlunr will support configuration that user could set how to combine the results from each field, such as "most_field" or "top_field".

5.2.3 Token Expandation

Sometimes user want to expand a query token to increase RECALL, then user could set expand model to true by configuration, default is false. For example, user query token is "micro", and assume "microwave" and "microscope" are in the index, then is user choose expand the query token "micro" to increase RECALL, both "microwave" and "microscope" will be returned and search in the index. The query results from expanded tokens are penalized because they are not exactly the same as the query token.

index.search("micro", {
    fields: {
        title: {boost: 2, bool: "AND"},
        body: {boost: 1}
    },
    bool: "OR",
    expand: true
});

Field level expand configuration will overwrite global expand configuration.

index.search("micro", {
    fields: {
        title: {
            boost: 2,
            bool: "AND",
            expand: false
        },
        body: {boost: 1}
    },
    bool: "OR",
    expand: true
});

6. Add customized stop words

Elasticlunr.js contains some default stop words of English, such as:

  • a
  • about
  • an
  • all
  • also
  • and
  • any
  • but
  • the
  • ...

Defaultly elasticlunr.js contains 120 stop words, user could decide not use these default stop words or add customized stop words.

6.1 Remove default stop words

You could remove default stop words simply as:

elasticlunr.clearStopWords();

6.2 Add customized stop words

User could add a list of customized stop words.

var customized_stop_words = ['an', 'hello', 'xyzabc'];
elasticlunr.addStopWords(customized_stop_words);

7. Use elasticlunr in Node.js

Elasticlunr support Node.js, you could use elastilunr in node.js as a node-module.

Install elasticlunr by:

npm install elasticlunr

then in your node.js project or in node.js console:

var elasticlunr = require('elasticlunr');

var index = elasticlunr(function () {
    this.addField('title')
    this.addField('body')
});

var doc1 = {
    "id": 1,
    "title": "Oracle released its latest database Oracle 12g",
    "body": "Yestaday Oracle has released its new database Oracle 12g, this would make more money for this company and lead to a nice profit report of annual year."
}

var doc2 = {
    "id": 2,
    "title": "Oracle released its profit report of 2015",
    "body": "As expected, Oracle released its profit report of 2015, during the good sales of database and hardware, Oracle's profit of 2015 reached 12.5 Billion."
}

index.addDoc(doc1);
index.addDoc(doc2);

index.search("Oracle database profit");

Other Languages

Default supported language of elasticlunr.js is English, if you want to use elasticlunr.js to index other language documents, then you need to use elasticlunr.js combined with lunr-languages.

Other languages example in Browser

Suppose you are using elasticlunr.js in browser for other languages, you could download the corresponding language support from lunr-languages, then include the scripts as:

<script src="lunr.stemmer.support.js"></script>
<script src="lunr.de.js"></script>

then, you could use elasticlunr.js as normal:

var index = elasticlunr(function () {
    // use the language (de)
    this.use(elasticlunr.de);
    // then, the normal elasticlunr index initialization
    this.addField('title')
    this.addField('body')
});

Pay attention to the special code:

    this.use(elasticlunr.de);

If you are using other language, such as es(Spanish), download the corresponding lunr.es.js file and lunr.stemmer.support.js, and change the above line to:

    this.use(elasticlunr.es);

Other languages example in Node.js

Suppose you are using elasticlunr.js in Node.js for other languages, you could download the corresponding language support from lunr-languages, put the files lunr.es.js file and lunr.stemmer.support.js in your project, then in your Node.js module, use elasticlunr.js as:

var elasticlunr = require('elasticlunr');
require('./lunr.stemmer.support.js')(elasticlunr);
require('./lunr.de.js')(elasticlunr);

var index = elasticlunr(function () {
    // use the language (de)
    this.use(elasticlunr.de);
    // then, the normal elasticlunr index initialization
    this.addField('title')
    this.addField('body')
});

For more details, please go to lunr-languages.

Contributing

See the CONTRIBUTING.mdown file.