flexsearch VS elasticlunr.js

Full-text search is powered by FlexSearch and Nextra will index all of your pages at build time ⚡.

I have a web page that reads in various .md files and displays them as HTML. The app uses the marked library to convert the markdown into HTML for display. I create a flexsearch search index out of the raw text values from the documents (raw text is gathered using DOMParser over all HTML elements) so that user can search for keywords in the docs and get back a table of results. The order of operations and search index code looks like:

I am trying to get flexsearch (a lib written in js) up and running in a TS project and found a working example here. I downloaded the project and ran 'yarn add flexsearch' and also 'yarn add @/types/flexsearch' since I know that you need a special index.d.ts file to convert the JS to TS properly.... however the code errors out during the Index object creation with the message.

Try using a proper browser search like Lunr or Flexsearch

Current version of FlexSearch (0.7.2) is not typo tolerant, see https://github.com/nextapps-de/flexsearch/issues/118

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 ?

I actually looked into this term before localeCompare(): Full Text Search. It's pretty heavy duty. In JavaScript, this can come in the form of a library dependency like FlexSearch. Far too bulky for the humble sorting task I have at hand.

Javascript seems to have a comprehensive in memory solution https://github.com/nextapps-de/flexsearch

Another option that was often suggested to me was building the search index with a library such as https://github.com/nextapps-de/flexsearch and distribute the index than to the client and handle it one the client. But yeah sounds like a lot of overhead and I haven't tried it.

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.