flexsearch VS lunr.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.

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.