flexsearch

Next-generation full-text search library for Browser and Node.js

Runssource: GitHubJavaScriptApache-2.0commit f7ed963096a0

JavaScript, Apache-2.0 licensed. The project labels itself: elasticsearch, full text search, fulltext search, fuzzy, fuzzy search, javascript, javascript library and nodejs.

flexsearch runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

FlexSearch v0.8.215 installs, builds (minus Google Closure Compiler minification due to missing Java), and passes 125/126 core tests covering search, async operations, caching, context-aware search, document search, tag search, custom encoders, result highlighting, GitHub issues, resolver, scoring, serialize/export, tokenization, worker threads, and keystore.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.25 (measured)
recorded runs
2
last tested
stars
13,820
forks
527
open issues
40
watchers
94
size
7 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing flexsearch, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Root package.json lacks "type": "module", causing ES module imports from test/ to src/ to fail with SyntaxError because Node 18 treats .js as CommonJS when no parent package.json declares type=module5 minutes
Install time
under a minute
Cold machine to finish
34 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npx mocha basic.js cache.js context.js document.js document.tag.js encoder.js highlight.js issues.js resolver.js scoring.js serialize.js tokenize.js worker.js keystore.js --exit -- flexsearch.bundle.min exited 0: 125 passing, 1 pending
Model tokens used
127,212
Exact commit tested
f7ed963096a0
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

\"" in /work/repo
 succeeded in 1205ms:
een resolved a Resolver properly (Document Worker) (68ms)
  Keystore
    ✔ Should have applied the keystore properly
    ✔ Should have extended the default limit
  125 passing (612ms)
  1 pending
 Warning: Cannot find any files matching pattern "flexsearch.bundle.min"
Return: 0
tokens used
127,212

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.5 minutes, faster than the median of the 4 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 5 elasticsearch projects Argusic has installed and timed, flexsearch was the 1st fastest to reach a running state, and 4 of 5 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.5 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.25
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

elasticsearchfull-text-searchfulltext-searchfuzzyfuzzy-searchjavascriptjavascript-librarynodejsopen-sourcesearchsearch-algorithmsearch-enginesearch-in-textsearchingsearching-algorithmswebweb-worker

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/flexsearch.svg)](https://argusic.com/subject/flexsearch)

Questions

Does flexsearch run?
Yes. flexsearch runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test flexsearch?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f7ed963096a0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test flexsearch?
The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does flexsearch take to install?
0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does flexsearch need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing flexsearch?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does flexsearch compare with the alternatives?
Of the 5 elasticsearch projects Argusic has installed and timed, flexsearch was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for flexsearch?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion