node-firestore-import-export

Firestore data import and export

Runssource: GitHubhomepageTypeScriptMITcommit 58db1841731d

TypeScript, MIT licensed. The project labels itself: backup, export, firebase, firestore, import and restore.

node-firestore-import-export runs. An Argusic agent installed it in 30 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install exits 0, npm run build runs the suite with 26 passing tests and compiles TypeScript, all three CLI binaries answer 1.1.0, and export/import/clear completed against the Firestore emulator on localhost:8080 with seeded and imported data verified through direct SDK reads.

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.31 (measured)
recorded runs
1
last tested
stars
390
forks
85
open issues
90
watchers
4
size
1 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 node-firestore-import-export, 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.

  • npm install's prepare script failed: `snyk protect` returned 'Authentication failed. Please check the API token on https://snyk.io'10 minutes
  • Firestore emulator would not start: Java not installed in container8 minutes
Install time
30 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm install exited 0; npm run build exited 0 with '26 passing'; firestore-export --version returned 1.1.0; FIRESTORE_EMULATOR_HOST=localhost:8080 node dist/bin/firestore-export.js -a /tmp/nfie-test/credentials.json -b /tmp/nfie-test/export.json --prettyPrint exited 0 and export.json contained users/alice {name:Alice,age:30} plus nested posts/p1 {title:Hello}; firestore-import -y exited 0 and direct SDK read-back of imported/doc1 returned {flag:true,count:7,name:Imported} with nested sub/c1 {v:nested}; firestore-clear -n users --yes --noWait exited 0 and direct SDK read-back of users/alice returned exists=false while imported/doc1 remained; re-export (export2.json) contained imported/doc1
Model tokens used
1,392,618
Exact commit tested
58db1841731d
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.

1,392,618
All verification is complete and the emulator-based end-to-end cycle passed. Summary of what was do…
**What happened**
- Clean `npm install` now exits 0 (patched `package.json` `prepare` to drop the Snyk step that hard…
- `npm run build` exits 0: 26 passing tests, then TypeScript compile to `dist/`.
- All three CLIs answer `--version` with `1.1.0`.
- Firestore emulator on `localhost:8080` answered `200` on HTTP probe.
- Export: seeded `users/alice` + nested `posts/p1`, then `firestore-export` produced JSON containin…
- Import: imported `imported/doc1` with nested `sub/c1`; direct SDK read-back confirmed `{flag:true…
- Clear: `firestore-clear -n users` removed `users/alice` (read back as false) while leaving `impor…
- Re-export after import contained `imported/doc1` with nested data.
Two errors were hit and fixed: Snyk auth failure in `prepare` (fixed in `package.json:30`), and mis…

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 2 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 MIT, as reported by its host.

What did not, or is not known

  • Took 30 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, node-firestore-import-export was the 47th fastest to reach a running state, and 32 of 48 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 Runner1/3Runs100.000.31

Topics (from GitHub)

backupexportfirebasefirestoreimportrestore

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/node-firestore-import-export.svg)](https://argusic.com/subject/node-firestore-import-export)

Questions

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

Discussion