vue-quill
Rich Text Editor Component for Vue 3.
Runssource: GitHubhomepageTypeScriptMITcommit 8d327c5f209f
TypeScript, MIT licensed. The project labels itself: editor, quill, text editor, vue, vue component, vue3 and wysiwyg editor.
vue-quill runs. An Argusic agent installed it in 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, production build produces all 8 dist bundles for all 4 formats, and all 13 test suite assertions pass.
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.
- chalk v5 ESM-only: scripts/chalk.js require() of ESM chalk failed2 minutes
- serialize-javascript crypto is not defined in rollup on Node 181 minute
- quill and quill-delta dependencies not installed for workspace package0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx tsx --test packages/vue-quill/src/components/moduleRegistration.test.mjs packages/vue-quill/src/components/QuillEditor.test.ts packages/vue-quill/src/assets/snow.test.ts exited 0, 13 passed
- Model tokens used
- 172,847
- Exact commit tested
- 8d327c5f209f
- 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.
Here's the final summary:
**Install**: `npm install` succeeded (640 packages, engine warnings for Node 18). Additional per-pa…
**Build**: `npm run build -- vue-quill` succeeded, producing all 8 dist bundles (dev + minified) ac…
**Tests**: `npx tsx --test` ran all 13 test assertions across 3 test files — all passed:
- QuillEditor toolbar prop: 2/2
- QuillEditor module registration: 1/1
- Snow theme list styles: 1/1
- Module registration names: 9/9
**Errors encountered**:
1. **chalk v5 ESM-only** — `scripts/chalk.js` used `require('chalk')` but chalk v5 is ESM-only. **F…
2. **serialize-javascript crypto not defined** — Node 18 rollup subprocess has no global `crypto`, …
3. **Missing quill-delta types** — workspace package `@vueup/vue-quill`'s dependencies (`quill`, `q…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 MIT, as reported by its host.
What did not, or is not known
- Took 10 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 editor projects Argusic has installed and timed, vue-quill was the 4th fastest to reach a running state, and 5 of 6 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.
- A quick evaluation: it was running 10 minutes after the clone.
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/vue-quill)Questions
- Does vue-quill run?
- Yes. vue-quill runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test vue-quill?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8d327c5f209f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test vue-quill?
- 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 vue-quill take to install?
- 10 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 vue-quill need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vue-quill?
- 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 vue-quill compare with the alternatives?
- Of the 6 editor projects Argusic has installed and timed, vue-quill was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for vue-quill?
- 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.