elasticlunr vs flexsearch vs fuse.js vs lunr vs search-index
JavaScript Search Libraries
elasticlunrflexsearchfuse.jslunrsearch-indexSimilar Packages:

JavaScript Search Libraries

JavaScript search libraries provide tools for implementing search functionality within web applications. These libraries can index data, perform searches, and return results based on user queries. They vary in features, performance, and complexity, catering to different use cases such as simple text search, full-text search, and search with advanced features like ranking, highlighting, and fuzzy matching. Choosing the right search library depends on factors like the size of the dataset, the complexity of search queries, and the need for features like real-time indexing or multi-language support.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
elasticlunr02,076-7710 years agoMIT
flexsearch013,6472.33 MB307 months agoApache-2.0
fuse.js020,045456 kB7a year agoApache-2.0
lunr09,215-1296 years agoMIT
search-index01,425693 kB5a year agoMIT

Feature Comparison: elasticlunr vs flexsearch vs fuse.js vs lunr vs search-index

Indexing Method

  • elasticlunr:

    elasticlunr creates an inverted index in memory, allowing for efficient search operations. It supports custom tokenization and stemming, making it flexible for different types of text data.

  • flexsearch:

    flexsearch offers multiple indexing strategies, including traditional inverted indexing and a more memory-efficient approach. It supports real-time indexing and allows for fine-tuning of the indexing process, making it highly versatile.

  • fuse.js:

    fuse.js does not create a traditional index. Instead, it builds a lightweight, in-memory structure that supports fuzzy searching. This approach is simple and effective for small to medium datasets but may not scale well for larger datasets.

  • lunr:

    lunr builds a compact inverted index that is stored in memory. It supports multi-field indexing, custom tokenization, and provides a simple API for searching. The index is created once and used for fast search queries.

  • search-index:

    search-index creates a full-text index using inverted indexing. It supports real-time indexing, multi-field indexing, and allows for complex queries. The indexing process is highly configurable, making it suitable for dynamic datasets.

Fuzzy Search Support

  • elasticlunr:

    elasticlunr supports basic fuzzy searching through configurable edit distance. It allows for approximate matching, but the implementation is relatively simple compared to more advanced libraries.

  • flexsearch:

    flexsearch provides advanced fuzzy search capabilities with configurable algorithms. It allows for fine-tuning the fuzziness level, making it one of the most feature-rich libraries for fuzzy searching.

  • fuse.js:

    fuse.js is known for its fuzzy search capabilities, allowing for approximate matching of strings. It provides configurable fuzziness, making it easy to adjust the sensitivity of the search.

  • lunr:

    lunr does not natively support fuzzy searching. However, it can be extended with plugins to add this feature. By default, it focuses on exact and partial matches.

  • search-index:

    search-index supports fuzzy searching as part of its full-text search capabilities. It allows for configurable fuzziness, making it suitable for applications that require approximate matching.

Real-time Indexing

  • elasticlunr:

    elasticlunr does not support real-time indexing out of the box. Indexing is done manually, and the library is designed for static or semi-static datasets.

  • flexsearch:

    flexsearch supports real-time indexing, allowing for updates to the index without needing to rebuild it. This feature makes it suitable for dynamic applications where data changes frequently.

  • fuse.js:

    fuse.js does not support real-time indexing as it requires the dataset to be loaded into memory before searching. However, the dataset can be updated dynamically, and the search will reflect the changes immediately.

  • lunr:

    lunr does not support real-time indexing. The index is built once and cannot be updated without rebuilding it. This makes it more suitable for static datasets.

  • search-index:

    search-index supports real-time indexing, allowing for continuous updates to the index as new data is added. This feature is ideal for applications with frequently changing data.

Memory Usage

  • elasticlunr:

    elasticlunr is lightweight and has a low memory footprint, making it suitable for client-side applications. However, memory usage increases with the size of the dataset due to the in-memory index.

  • flexsearch:

    flexsearch is designed to be memory-efficient, especially with its configurable indexing options. It uses advanced algorithms to minimize memory usage while providing fast search performance.

  • fuse.js:

    fuse.js has a low memory footprint, making it suitable for small to medium datasets. However, memory usage can increase significantly with larger datasets due to its in-memory search structure.

  • lunr:

    lunr is relatively memory-efficient for the features it provides. However, memory usage grows with the size of the dataset, particularly during indexing.

  • search-index:

    search-index can be memory-intensive, especially with large datasets, due to its full-text indexing approach. However, it provides options for optimizing memory usage during indexing and searching.

Ease of Use: Code Examples

  • elasticlunr:

    Simple Search with elasticlunr

    const elasticlunr = require('elasticlunr');
    const index = elasticlunr(function () {
      this.addField('title');
      this.addField('body');
      this.setRef('id');
    });
    
    index.addDoc({ id: 1, title: 'Hello World', body: 'This is a test document.' });
    index.addDoc({ id: 2, title: 'Elastic Search', body: 'Searching with elasticlunr.js.' });
    
    const results = index.search('test');
    console.log(results);
    
  • flexsearch:

    Simple Search with flexsearch

    const FlexSearch = require('flexsearch');
    const index = new FlexSearch.Index();
    
    index.add(1, { title: 'Hello World', body: 'This is a test document.' });
    index.add(2, { title: 'Elastic Search', body: 'Searching with flexsearch.' });
    
    index.search('test').then(results => {
      console.log(results);
    });
    
  • fuse.js:

    Simple Fuzzy Search with fuse.js

    const Fuse = require('fuse.js');
    const data = [
      { id: 1, title: 'Hello World', body: 'This is a test document.' },
      { id: 2, title: 'Elastic Search', body: 'Searching with fuse.js.' },
    ];
    
    const fuse = new Fuse(data, { keys: ['title', 'body'], threshold: 0.3 });
    const results = fuse.search('test');
    console.log(results);
    
  • lunr:

    Simple Search with lunr

    const lunr = require('lunr');
    const index = lunr(function () {
      this.ref('id');
      this.field('title');
      this.field('body');
    });
    
    index.add({ id: 1, title: 'Hello World', body: 'This is a test document.' });
    index.add({ id: 2, title: 'Elastic Search', body: 'Searching with lunr.js.' });
    
    const results = index.search('test');
    console.log(results);
    
  • search-index:

    Simple Search with search-index

    const si = require('search-index');
    const index = si({ name: 'my-index' });
    
    index({ id: 1, title: 'Hello World', body: 'This is a test document.' });
    index({ id: 2, title: 'Elastic Search', body: 'Searching with search-index.' });
    
    index.search('test').then(results => {
      console.log(results);
    });
    

How to Choose: elasticlunr vs flexsearch vs fuse.js vs lunr vs search-index

  • elasticlunr:

    Choose elasticlunr if you need a lightweight, client-side search library that mimics Elasticsearch's API. It's great for small to medium datasets and offers features like stemming, tokenization, and custom scoring.

  • flexsearch:

    Choose flexsearch if you require a high-performance, feature-rich search library with support for fuzzy searching, multi-language indexing, and real-time updates. It is suitable for applications that need fast search capabilities with minimal memory usage.

  • fuse.js:

    Choose fuse.js if you need a simple, lightweight library for fuzzy searching within a dataset. It works well for small to medium-sized datasets and allows for easy configuration of search algorithms, making it ideal for applications that require approximate matching.

  • lunr:

    Choose lunr if you want a simple, self-contained full-text search library that creates an index in the browser. It is suitable for static sites or applications with a fixed dataset, providing fast search capabilities without the need for a server.

  • search-index:

    Choose search-index if you need a full-featured, Node.js-based search indexing solution that supports real-time indexing, multi-field search, and advanced features like faceting and ranking. It is ideal for applications that require more control over the indexing and search process.

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.