generator-office

Yeoman generator for building Microsoft Office related projects.

Runssource: GitHubhomepageTypeScriptMITcommit 106a1cf50c2e

TypeScript, MIT licensed. The project labels itself: add ins, office, yeoman generator and yo office.

generator-office runs. An Argusic agent installed it in 12 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.

The generator-office repo installs from the public npm registry, builds, and its full mocha suite passes 38/38; a real 'yo office' run generates a valid Excel taskpane project that builds with webpack, validates its manifest, and serves its taskpane/JS/manifest over HTTP 200.

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 72.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
72.5 / 100
cost of the verifying run
$0.49 (measured)
recorded runs
2
last tested
stars
959
forks
225
open issues
9
watchers
71
size
23 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 generator-office, 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 failed E401/E404 because repo .npmrc and bundled package-lock.json pointed to a private Azure feed (office.pkgs.visualstudio.com)5 minutes
  • System Node is v18 but the repo requires >=20.12; npm install unsupported-engine and build steps fail4 minutes
  • First npm test run had 1 failure in the proxy-config test; the npx/mocha subprocess hit the private feed2 minutes
  • Generated project's npm start fails because CA-cert install needs sudo (unavailable) and Office sideload is unsupported on linux; not fixable in this container1 minute
Install time
12 minutes
Cold machine to finish
84 minutes
Errors hit and fixed
4 hit, 3 fixed with no human help
How the result was proved
npm run build exited 0 (tsc+copy); npm test exited 0 with 38 passing, 0 failing; yo office generated '/tmp/yo-run/My Test App'; its npm run build compiled webpack successfully, npm run validate printed 'The manifest is valid.', and curl on localhost:8977 returned 200 for taskpane.html, taskpane.js, and manifest.xml
Model tokens used
1,077,421
Exact commit tested
106a1cf50c2e
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,077,421
**Done.** The repository works end-to-end as a brand-new user. Here's my report.
**What fixed the repo**
- **Node engine mismatch** — system Node is v18 but the repo requires `>=20.12`. Installed Node v22…
- **Private-registry auth failure** — repo `.npmrc` and the bundled `package-lock.json` pointed to …
- **`npm start` sideload limit** — `office-addin-debugging` needs `sudo` to install a dev CA cert a…
**Verified (all observed directly)**
- `npm install` → 717 packages audited, no errors.
- `npm run build` → `tsc` and `copy` both exit 0.
- `npm test` → **38 passing, 0 failing** (2m).
- `yo office --projectType taskpane --name "My Test App" --host excel --ts true` → real CLI launche…
- Generated project: `npm run build` → webpack compiled successfully; `npm run validate` → "The man…

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 12 minutes.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Hit 4 errors during setup, 1 of which were not solved.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs95.000.49
Argusic Runner1/3Did not run50.000.86

Topics (from GitHub)

add-insofficeyeoman-generatoryo-office

Embed the badge

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

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

Questions

Does generator-office run?
Yes. generator-office runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test generator-office?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 106a1cf50c2e. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test generator-office?
The run that produced this verdict cost $0.49: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does generator-office take to install?
12 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 generator-office need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing generator-office?
4 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.
Where is the evidence for generator-office?
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