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 10.5 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 dist files built (dexie.js, dexie.mjs, dexie.min.js, modern/dexie.mjs, modern/dexie.min.mjs, dexie.d.ts) and all 309 QUnit tests pass in Chromium 127 headless via Karma.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- just-build v0.9.24 whichLocal misparses pnpm v10+ shell shims, picks up `elif` as binary path3 minutes
- No Chromium/Chrome browser installed3 minutes
- pnpm not found on PATH1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- karma start test/karma.custom.conf.js --single-run returned exit 0: 309 tests completed (QUnit, 14.5s) in ChromiumHeadless 127; typings compiled with tsc exit 0
- Model tokens used
- 378,366
- 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.
2026-09-26T13:28:45.051440Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… tokens used 378,366 All 309 tests passed, confirming the build is fully functional. Here's the summary: **Install:** Dependencies installed via `pnpm install` (1216 packages). Build completed manually si… **Test suite:** 309 QUnit tests passed in Chromium 127 headless via Karma. Typings compiled success… **Errors encountered:** | Error | Fix | Time | |---|---|---| | `pnpm: not found` — not on PATH | Installed pnpm to `~/.npm-global/bin` and added to PATH | 1 | | `just-build default failed. Cannot find module '/work/repo/node_modules/.bin/elif'` — `just-build… | `Cannot start Chrome` — no Chromium binary in container | Installed Playwright's Chromium (`npx p…
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.
What did not, or is not known
- Took 10.5 minutes to install, slower than the median of the 19 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 20 database projects Argusic has installed and timed, Dexie.js was the 18th fastest to reach a running state, and 17 of 20 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](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 11 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. One attempt is 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.07: 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?
- 10.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 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 20 database projects Argusic has installed and timed, Dexie.js was the 18th fastest to reach a running state, and 17 of 20 reached one at all.
- Where is the evidence for Dexie.js?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.