lin-cms-vue
🔆 Vue+ElementPlus构建的CMS开发框架
Runssource: GitHubhomepageJavaScriptMITcommit 16d358882540
JavaScript, MIT licensed. The project labels itself: cms, element plus, vue, vue admin, vue cli3, vue cms, vue router and vue3.
lin-cms-vue runs. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
lin-cms-vue Vue 3 CMS frontend installs dependencies, builds to dist/, and the dev server serves HTTP 200 at localhost:8080.
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.
- jest.config.js referenced 'vue-jest' which is not available; @vue/vue3-jest needed for Vue 33 minutes
- Presence of yarn.lock triggers mandatory yarn check during npm run serve; yarn is not installed and cannot be installed (no root)2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run build produced dist/ with index.html (81 lines); npm run serve started on localhost:8080, curl returned HTTP 200 with 2603 bytes of <!DOCTYPE html>
- Model tokens used
- 59,238
- Exact commit tested
- 16d358882540
- 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.
Build finished at 16:22:43 by 0.000s exec /bin/sh -lc 'pkill -f "vue-cli-service" 2>/dev/null; echo "done"' in /work/repo exited 143 in 0ms: exec /bin/sh -lc 'cd /work/repo && git checkout -- package.json package-lock.json yarn.lock 2>/dev/null;… succeeded in 0ms: yarn.lock Now I have all the information. Let me compile the final structured report. tokens used 59,238 Now I have all the information. Let me compile the final structured report.
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 8 minutes, faster than the median of the 9 comparable projects Argusic has measured.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 10 cms projects Argusic has installed and timed, lin-cms-vue was the 5th fastest to reach a running state, and 9 of 10 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 8 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)
cmselement-plusvuevue-adminvue-cli3vue-cmsvue-routervue3vuex
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lin-cms-vue)Questions
- Does lin-cms-vue run?
- Yes. lin-cms-vue runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test lin-cms-vue?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 16d358882540. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lin-cms-vue?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lin-cms-vue take to install?
- 8 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 lin-cms-vue need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lin-cms-vue?
- 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 lin-cms-vue compare with the alternatives?
- Of the 10 cms projects Argusic has installed and timed, lin-cms-vue was the 5th fastest to reach a running state, and 9 of 10 reached one at all.
- Where is the evidence for lin-cms-vue?
- 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.