Skip to content
forked from olivernn/lunr.js

A bit like Solr, but much smaller and not as bright

License

Notifications You must be signed in to change notification settings

ming300/lunr.js

 
 

Repository files navigation

Lunr.js

Build Status

A bit like Solr, but much smaller and not as bright.

Example

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

var idx = lunr(function () {
    this.field('title', { boost: 10 })
    this.field('body')
})

Adding documents to be indexed is as simple as:

var doc = {
    "title": "Twelfth-Night",
    "body": "If music be the food of love, play on: Give me excess of it…",
    "author": "William Shakespeare",
    "id": 1
}    
idx.add(doc)

Then searching is as simple:

idx.search("love")

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

[{
    "ref": 1,
    "score": 0.87533
}]

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

Description

Lunr.js is a small, full-text search library for use in the browser. It indexes JSON documents and provides a simple search interface for retrieving documents that best match text queries.

Why

For web applications with all their data already sitting in the client, it makes sense to be able to search that data on the client too. It saves adding extra, compacted services on the server. A local search index will be quicker, there is no network overhead, and will remain available and useable even without a network connection.

Installation

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

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

Contributing

Contributions are very welcome, to make the process as easy as possible please follow these steps:

  • Open an issue detailing the bug you've found, or the feature you wish to add. Simplified working examples using something like jsFiddle make it easier to diagnose your problem.
  • Add tests for your code (so I don't accidentally break it in the future)
  • Don't change version numbers or make new builds as part of your changes
  • Don't change the built versions of the library, only make changes to code in the lib directory'

Developer Dependencies

A JavaScript runtime is required for building the library.

Run the tests with, this will use phantomjs to run the tests:

make test

The tests can also be run in the browser by starting the test server:

make server

This will start a server on port 3000, the tests are then available at '/test'

About

A bit like Solr, but much smaller and not as bright

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 97.6%
  • CSS 1.8%
  • Shell 0.6%