flexsearch VS TNTSearch

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.

FWIW an alternative might be to have your endpoint perform the full text search server-side with something like https://github.com/teamtnt/tntsearch. No external search service required.

While we're at it, would it be possible to store the index in the existing database instead of SQLite ? Wouldn't that allow for index syncing reliability (I hear there are file corruption problems ) ? And reducing the number of processes (no index queue) ?

As you saw from the tutorial, adding a full-text search to your project is pretty straightforward. We covered only the tip of the iceberg here. TNTSearch is a powerful engine that can do a lot of stuff - even classification if that's something you might need. For more info, you can check out the GitHub documentation.