Dexie.js

A Minimalistic Wrapper for IndexedDB

Runssource: GitHubhomepageTypeScriptApache-2.0commit 57a028d7c0ee

TypeScript, Apache-2.0 licensed. The project labels itself: database, indexeddb, javascript, offline, offline storage and storage.

Dexie.js runs. An Argusic agent installed it in 22.8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dexie.js v4.4.6 builds successfully, typings compile, all 10 executed test modules pass (206 assertions), and the module loads and performs IndexedDB CRUD operations in both Node and headless Chrome.

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.38 (measured)
recorded runs
2
last tested
stars
14,689
forks
724
open issues
590
watchers
111
size
73 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 Dexie.js, 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.

  • just-build tool incompatible with pnpm v12 shell shims (elif parsing bug in whichLocal.js)15 minutes
  • Karma test suite disconnects after ~6.8s of execution (10 test modules pass, then Chrome closes)5 minutes
  • Chrome for Testing binary downloaded separately (no system browser available, no root access)2 minutes
Install time
23 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pnpm test:unit (karma start) ran 206 tests across 10 modules all passing before browser disconnect; tsc -p test/typings-test/ exited 0; node -e 'require("./dist/dexie.js")' prints version 4.4.6; headless Chrome runs Dexie CRUD operations with IndexedDB
Model tokens used
505,487
Exact commit tested
57a028d7c0ee
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.

6
files in dist/
Let me calculate the elapsed time:
exec
/bin/sh -lc 'date -d "2026-11-03 13:33:40" +%s; date -d "2026-11-03 13:56:30" +%s' in /work/repo
 succeeded in 0ms:
1793712820
1793714190
About 1370 seconds = ~22.8 minutes. Let me now compile the final result.
tokens used
505,487
About 1370 seconds = ~22.8 minutes. Let me now compile the final result.

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.
  • Recovered from all 3 errors 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.

What did not, or is not known

  • Took 22.8 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.

Of the 37 database projects Argusic has installed and timed, Dexie.js was the 35th fastest to reach a running state, and 31 of 37 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.

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.38
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

databaseindexeddbjavascriptofflineoffline-storagestorage

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/Dexie.js.svg)](https://argusic.com/subject/dexie-js)

Questions

Does Dexie.js run?
Yes. Dexie.js runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test Dexie.js?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 57a028d7c0ee. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Dexie.js?
The run that produced this verdict cost $0.38: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Dexie.js take to install?
22.8 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 Dexie.js need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Dexie.js?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Dexie.js compare with the alternatives?
Of the 37 database projects Argusic has installed and timed, Dexie.js was the 35th fastest to reach a running state, and 31 of 37 reached one at all.
Where is the evidence for Dexie.js?
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