excalidraw tested by Argusic Runner

What the test found

Excalidraw installs, typechecks, lints, builds (app bundle, PWA service worker, and all six npm library packages) and passes its full 1862-test suite on Node 18, and the app runs and is interactively usable in a real browser from both the dev server on port 3001 and the served production build.

No third-party keys were required, so no mocks were needed. The Firebase config and json-dev.excalidraw.com endpoints in .env.development are only exercised by real-time collaboration and shareable-link export; the editor loads and functions fully without them. Verification was genuine end-to-end rather than mock-based: the repo's own vitest suite (1862 tests) passed, and both the dev server and the production bundle were driven in a real headless Chrome, where a rectangle was drawn by actual mouse-down/move/up on the canvas and read back from localStorage as a 250x180 rectangle element with zero page or console errors (a screenshot confirmed the toolbar, properties panel and hand-drawn shape render correctly). Two documentation/config mismatches a new user would hit but which I deliberately did not change: the dev docs say http://localhost:3000 while .env.development sets VITE_APP_PORT=3001, and `yarn start` shells out to a nested `yarn` that re-runs the failing engine check. The repository working tree is unmodified (git status clean); every fix was environmental. Non-blocking noise observed: caniuse-lite is 18 months stale, @typescript-eslint warns TypeScript 5.9.3 is past its supported range, and the production build logs benign Chrome 'unload is not allowed' permissions-policy notices.

Argusic installed excalidraw in 2 minutes and launched it; verification reached Verified running for real. 5 of 5 recorded errors were worked through (see the timeline below).

Runsall runs of excalidraw

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.