← lodash/lodash
CodeVetter · Repo Unpack · Behavior traces

lodash/lodash

Scanned commit 2b5e6f7399 dated 2026-09-11 — last upstream commit. Generated by codevetter codevetter 1.12.0 on 2026-09-22. Deep analysis by claude-opus-5 via the claude CLI on 2026-09-22 (396s).

Four flows matter here: library initialization, an FP conversion, the `npm test` path, and the browser-test path. Library init is entirely synchronous at require time. The Node test path is unusual because `pretest` forces a full build first, meaning `npm test` cannot run without webpack and uglify succeeding. The browser path is a three-stage `document.write` cascade that deliberately corrupts globals before loading lodash, snapshots the result as `lodashBizarro`, restores the globals, then loads the real build and the suite.