Eve library

Node dependency setup · 2026-09-08

Guide

Revision 1

On this page

This receipt closes the destination-host dependency setup checkbox. The repository's declared package manager is pnpm 10.25.0; the installed executable reports 10.25.0 under Node 24.15.0, which satisfies the declared Node 22+ engine.

Installation and resolution#

The memory-supervised command pnpm install --frozen-lockfile exited 0. A baseline diff proves that package.json, pnpm-lock.yaml, pnpm-workspace.yaml and apps/oshun/web/package.json did not change during setup.

From the @oshun/web package context:

  • @playwright/test and playwright resolve at 1.60.0;
  • axe-core resolves at 4.11.4 and its minified browser script is readable;
  • the Playwright-managed Chromium executable exists and launches headlessly as Chromium 148.0.7778.96.

The optional channel: "chrome" probe fails because /opt/google/chrome/chrome is absent. The prior Chrome 152.0.7977.76 captures remain valid evidence for their recorded revision and environment; they are not relabelled as current-host runs.

Install warnings and boundary#

pnpm emitted warnings while linking executable shims whose workspace targets are build outputs not present in the clean source tree. Most point to the oshun-codex-openai / oshun-opencode-openai CLI under an unbuilt local @oshun/ai package; the remainder point to the unbuilt kalika-research-ops CLI entry. The install still exited 0 and the required Playwright and accessibility packages resolve and run. This receipt establishes dependency setup for the presentation/browser workflow. It does not claim that every local workspace CLI package has been built or that the whole monorepo has passed a production build.

The environment record retains exact versions, executable availability, warning counts and the resource floor observed during the supervised install. The self-verifier rechecks its hashes, package-manager pin, live package resolution, managed-browser launch, unchanged manifests and the closed TODO entry.