elasticlunr vs algoliasearch vs fuse.js vs js-search vs lunr vs search-index
JavaScript Search Libraries
elasticlunralgoliasearchfuse.jsjs-searchlunrsearch-indexSimilar Packages:

JavaScript Search Libraries

JavaScript search libraries provide developers with tools to implement efficient search functionality in web applications. These libraries vary in their approach, capabilities, and performance, allowing developers to choose based on their specific needs such as indexing, searching speed, and ease of integration. They can handle various types of data and offer features like fuzzy searching, ranking, and advanced querying, enhancing user experience by making information retrieval faster and more intuitive.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
elasticlunr25,2232,076-7710 years agoMIT
algoliasearch01,3861.59 MB278 days agoMIT
fuse.js020,033456 kB7a year agoApache-2.0
js-search02,229117 kB83 years agoMIT
lunr09,213-1296 years agoMIT
search-index01,425693 kB5a year agoMIT

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

Search Algorithm

  • elasticlunr:

    ElasticLunr implements a simple inverted index search algorithm, which is efficient for small datasets. It supports basic features like stemming and stop words but lacks the advanced capabilities of larger search engines.

  • algoliasearch:

    AlgoliaSearch uses a highly optimized search algorithm that provides instant results with relevance ranking, typo tolerance, and customizable ranking criteria. It leverages advanced techniques like faceting and geo-search to enhance user experience.

  • fuse.js:

    Fuse.js employs a fuzzy search algorithm that allows for approximate string matching. It provides options for scoring and weighting different fields, making it flexible for various search scenarios.

  • js-search:

    js-search uses a basic keyword search algorithm that matches terms in the indexed data. It's straightforward but lacks advanced features like fuzzy matching or ranking.

  • lunr:

    Lunr uses an inverted index structure similar to ElasticLunr, allowing for efficient full-text search. It supports features like stemming and scoring, making it suitable for text-heavy applications.

  • search-index:

    Search Index combines both client-side and server-side indexing, allowing for complex queries and ranking. It supports full-text search and is designed for larger datasets.

Ease of Integration

  • elasticlunr:

    ElasticLunr is lightweight and requires minimal setup, making it easy to integrate into static sites or small applications without server-side dependencies.

  • algoliasearch:

    AlgoliaSearch is easy to integrate with various frameworks and platforms, offering SDKs for popular languages and a user-friendly dashboard for managing indices and settings.

  • fuse.js:

    Fuse.js is straightforward to implement with a simple API, allowing developers to quickly set up search functionality with minimal configuration.

  • js-search:

    js-search is designed for simplicity, requiring only basic JavaScript knowledge to integrate and use effectively in applications.

  • lunr:

    Lunr is easy to set up and use in client-side applications, with a simple API that allows for quick indexing and searching of documents.

  • search-index:

    Search Index requires more setup due to its comprehensive features, but it provides extensive documentation and examples to assist developers in integration.

Performance

  • elasticlunr:

    ElasticLunr performs well for small datasets but may struggle with larger collections due to its client-side nature and lack of advanced optimizations.

  • algoliasearch:

    AlgoliaSearch is optimized for speed, providing instant search results even with large datasets due to its hosted nature and advanced indexing techniques.

  • fuse.js:

    Fuse.js is efficient for small to medium datasets, but performance may degrade with very large datasets due to its fuzzy searching capabilities.

  • js-search:

    js-search is lightweight and performs adequately for small datasets but may not scale well for larger collections due to its basic search algorithm.

  • lunr:

    Lunr offers good performance for small to medium-sized datasets, but like ElasticLunr, it may face challenges with larger collections due to client-side limitations.

  • search-index:

    Search Index is designed for scalability and can handle larger datasets effectively, providing good performance for both client-side and server-side searches.

Advanced Features

  • elasticlunr:

    ElasticLunr offers basic features like stemming and stop words but lacks advanced capabilities found in more powerful search engines.

  • algoliasearch:

    AlgoliaSearch provides advanced features like typo tolerance, synonyms, geo-search, and analytics, making it a robust solution for complex search needs.

  • fuse.js:

    Fuse.js supports fuzzy searching, scoring, and customizable search options, allowing for a tailored search experience without being overly complex.

  • js-search:

    js-search is basic and does not offer advanced features, focusing instead on simplicity and ease of use for straightforward keyword searches.

  • lunr:

    Lunr supports features like stemming and scoring but does not include advanced functionalities like typo tolerance or synonym handling.

  • search-index:

    Search Index provides a comprehensive set of features, including full-text search, complex queries, and customizable indexing options, making it suitable for more demanding applications.

Community and Support

  • elasticlunr:

    ElasticLunr has a smaller community, but it is well-documented and easy to understand, making it accessible for new users.

  • algoliasearch:

    AlgoliaSearch has a strong community and extensive documentation, along with dedicated support options for users, making it easy to find help and resources.

  • fuse.js:

    Fuse.js has a growing community with good documentation and examples, providing sufficient resources for developers to get started.

  • js-search:

    js-search has limited community support but is straightforward enough that developers can often troubleshoot issues independently.

  • lunr:

    Lunr has a solid community and good documentation, making it easier for developers to find support and examples for implementation.

  • search-index:

    Search Index has a dedicated community and comprehensive documentation, offering various resources for troubleshooting and advanced usage.

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

  • elasticlunr:

    Select ElasticLunr for lightweight, client-side search capabilities with a simple API. It's suitable for smaller applications or static sites where you need to implement search without server-side dependencies.

  • algoliasearch:

    Choose AlgoliaSearch if you need a powerful hosted search solution with real-time indexing, advanced features like typo tolerance, and a customizable search experience. It's ideal for applications that require high performance and scalability.

  • fuse.js:

    Opt for Fuse.js if you require fuzzy searching capabilities and want to perform searches on small to medium datasets. It is easy to integrate and offers a flexible API for customizing search behavior.

  • js-search:

    Use js-search for a straightforward, lightweight search solution that is easy to set up. It's best for applications that need a simple keyword search without complex features or dependencies.

  • lunr:

    Choose Lunr if you want a full-text search solution that works in the browser. It's great for static sites and small applications, providing a balance between performance and ease of use.

  • search-index:

    Select Search Index if you need a more comprehensive solution that allows for both client-side and server-side search capabilities. It's suitable for applications requiring more advanced indexing and querying features.

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.