firestore-backup-restore
NPM package for backup and restore Firebase Firestore
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 0c2ed3ab1dff
TypeScript, MIT licensed. The project labels itself: backup, firebase, firestore, firestore database, firestore helper, hacktoberfest, npm package and restore.
firestore-backup-restore runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Package builds and all 25 tests pass using an in-memory Firestore mock that replaces firebase-admin and request-promise; no real credentials or emulator required.
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 92 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.
- No Java runtime — Firebase Emulator cannot start3 minutes
- Missing serviceAccountKey.json (gitignored, not shipped in repo)1 minute
- vitest config missing setupFiles entry1 minute
- Install time
- 7 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx vitest run --reporter verbose, 2 test files passed, 25 tests passed (12 parses + 13 firestore)
- Model tokens used
- 97,764
- Exact commit tested
- 0c2ed3ab1dff
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `npm run build` (`vite build`) succeeded, producing ES and CJS bundles in `dist/` **Test Results:** - `test/parses.spec.ts` — 12/12 passed (pure helper functions, no mock needed) - `test/firestore.spec.ts` — 13/13 passed after standing up a schema-correct Firestore mock **Errors encountered & fixes:** 1. **Missing `serviceAccountKey.json`** (in `.gitignore`, not shipped) — created a placeholder file… 2. **No Firebase Emulator** (no Java runtime) — built `test/setup.ts` providing an in-memory `Fires… 3. **`vitest.config.ts` missing setup files entry** — added `setupFiles: ['./test/setup.ts']`. 4. **Engine warnings** for `@firebase/*` packages requiring Node >=20 (container has v18.19.1) — no… **What currently works:** The package builds cleanly, and all 25 tests pass (12 parse helpers + 13 Firestore integration) usi… **Note:** `test/firestore.spec.ts` test "Restore data from API" tried to hit `firebasestorage.googl…
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 7 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 48 backup projects Argusic has installed and timed, firestore-backup-restore was the 34th fastest to reach a running state, and 32 of 48 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
backupfirebasefirestorefirestore-databasefirestore-helperhacktoberfestnpm-packagerestore
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/firestore-backup-restore)Questions
- Does firestore-backup-restore run?
- firestore-backup-restore runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test firestore-backup-restore?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0c2ed3ab1dff. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test firestore-backup-restore?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does firestore-backup-restore take to install?
- 7 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 firestore-backup-restore need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing firestore-backup-restore?
- 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 firestore-backup-restore compare with the alternatives?
- Of the 48 backup projects Argusic has installed and timed, firestore-backup-restore was the 34th fastest to reach a running state, and 32 of 48 reached one at all.
- Where is the evidence for firestore-backup-restore?
- 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.