elasticlunr.js VS lunr.js

When i did my static site search function some time ago, I used Elasticlunr. I was able to pregenerate the index file as a big json file that is loaded at the client.

http://elasticlunr.com/

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

Very nice! Seems to perform very well. I'm curious, have you compared Fuse with other search engines? Like flex search or elasticlunr? Why did you choose fuse ?

Check out elasticlunr

There's also Elasticlunr which is based off of lunr.js and is what mdBook uses

http://elasticlunr.com/

Does this relate to http://elasticlunr.com/? mdBook uses the latter, and I was wondering how I can parse/read its indexes from Python so I can provide my own search from them.

Same as above, for most blogs something like http://elasticlunr.com/ can get the job done really well.

3. HotSwap on the fly themes

Doctave comes with offline search built in. We use the elasticlunr-rs crate to generate a search index that is compatible with the elasticlunr.js library. You can see it in action by going to our docs (built with the CLI, naturally) and hitting the letter s on your keyboard to focus on the search bar. The searching happens entirely client-side.

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

Also search results can be pre-indexed and stored in a Json file. Just as an example. https://lunrjs.com/

Would anyone be willing to help make this more accessible and clean? I have some front-end dev experience, but it would be cool to work together with people to make sure we have something that makes sense and looks nicer than what I could do myself. As for functionality, searching on GitHub directly seems to work pretty well, but it might be better to have a page and a search feature maybe using something like Lunr. I would also like to create some sort of easy "API" in case Matt wants to embed some transcripts on his website. It would be cool if it would be as easy as just adding a blank div with a special id and a data attribute with the episode number on the Squarespace page.

which is open source, appears to be free, and claims that it can run in the browser

Is there a way to run it in WASM, to get something like Lunr[1]? We prefer to do our (small-index, <2MB) search client-side for a bunch of reasons, currently using Lunr.js, but it's a bit annoying and the typeahead search is something I improvised and not really official.

[1] https://lunrjs.com/

To ensure cross-platform compatibility, Bitwarden uses Lunr.js for searching. This search engine is a bit quirky, and difficult to get used to.

Slightly more js work required, but this should a more customisable solution: https://lunrjs.com/

OWDX runs entirely in the browser; as such, it cannot offer cutting-edge search functionality of the sort you'd find in a search engine or an expensive piece of enterprise software. The search library I'm using — lunr.js, for anyone who's interested — does, however, offer a nice set of core functionality and a modest but handy query language.