webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Runssource: GitHubJavaScriptMITcommit 089b4c064fc6
JavaScript, MIT licensed. The project labels itself: amd, build tool, commonjs, compiler, es2015, es6, esm and javascript.
webpack runs. An Argusic agent installed it in 4 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
webpack 5.111.1 installed, library loads, CLI builds bundles, and 160 unit test files pass under jest with --experimental-vm-modules
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 93.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- yarn not found in PATH for automated setup1 minute
- yarn not in PATH after npm install yarn to project0.5 minutes
- webpack --help fails with 'Invalid value used as weak map key'
- Install time
- 4 minutes
- Cold machine to finish
- 58 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- node bin/webpack.js --config compiled a production bundle (mode=production) and reported 'compiled successfully' with asset output; Jest unit tests (e.g. 5 suites, 59 tests) all passed
- Model tokens used
- 100,282
- Exact commit tested
- 089b4c064fc6
- 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.
2026-10-04T10:27:50.976746Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-04T10:27:50.977168Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
100,282
Now I have all the data I need. Here's the final summary:
**Install**: Ran `node setup/setup.js` (yarn installed via npm first since `WEBPACK_SETUP=automated…
**Verified**:
- Library loads correctly (`require("webpack")` → v5.111.1)
- Programmatic build (`webpack({...}, callback)`) produces bundle successfully
- CLI build (`node bin/webpack.js --config`) outputs "compiled successfully" and produces a minimiz…
- Jest unit tests pass across multiple batches (e.g., 5 suites/59 tests all passed)
**Known issue**: `webpack --help` hits a `WeakMap` bug in webpack-cli's commander integration — not…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 4 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 3 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.
- A quick evaluation: it was running 4 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 93.33 | 0.22 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.21 |
Topics (from GitHub)
amdbuild-toolcommonjscompileres2015es6esmjavascriptjavascript-compilerjavascript-modulesloadersmodule-bundlerpluginswebweb-performancewebpack
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/webpack)Questions
- Does webpack run?
- Yes. webpack runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test webpack?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 089b4c064fc6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test webpack?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does webpack take to install?
- 4 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 webpack need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing webpack?
- 3 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.
- Where is the evidence for webpack?
- 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.