minisearch VS flexsearch

I wrote an online catalog a while back (and I need to get back on adding graphics and products at some point). It’s written using Eleventy and the minisearch library. The source and data are available on Github if you want to see how I did things. I’m not a professional web designer either, but it was a fun project.

You could have a look at https://github.com/lucaong/minisearch/

If you're dealing with thousands of records or less, searching titles and summaries rather than long bodies of text, I recommend looking into client-side solutions. Nothing beats the responsiveness of search-as-you-type entirely on the client side. It can be fairly sophisticated fulltext search. For example, I've built had great success with MiniSearch.

I quite enjoy minisearch[1] which is also 0 dependencies, actively maintained, and I expect would work well in a worker environment. I dropped it into a service worker and plugged it with a simple point in polygon script to enable geosearch for a recent project[2] and it played v. nicely.

[1] https://github.com/lucaong/minisearch

No magic here, the underlying engine is Minisearch, which uses the BM25 algorithm (the de facto standard among search libraries). Omnisearch adds a magic sauce during indexing by converting notes into custom objects, with the following fields: - body (the plain markdown text) - filename & yaml aliases - level 1 headers - level 2 headers - level 3 headers

It's actually really simple! Minisearch did most of the heavy lifting so all we needed to do was the crawling, storing and UI etc. I'd check that out if you're interested in the search part!

We use MiniSearch for searching, while fast-fuzzy is used for highlighting of detected search terms.

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.