Problem
Contributors have to set up the toolchain manually (Node 22, pnpm) and discover on their own that integration tests need xvfb-run -a on headless environments. CI already uses this wrapper, but the docs and local setup do not reflect it.
Proposal
Add a .devcontainer/ configuration that matches CI:
- Base image with Node 22 (matching CI and
package.json engines)
- Pre-installed Chromium native libraries and
xvfb so pnpm test:integration works out of the box
pnpm install --frozen-lockfile on container creation- A short README with an "Open in Dev Containers" badge
- Dependabot tracking for the base image digest
- An AGENTS.md note documenting
xvfb-run -a for any headless environment
Outcome
One-click contributor environment that reproduces CI locally and removes a common source of first-run failures.
Problem
Contributors have to set up the toolchain manually (Node 22, pnpm) and discover on their own that integration tests need
xvfb-run -aon headless environments. CI already uses this wrapper, but the docs and local setup do not reflect it.Proposal
Add a
.devcontainer/configuration that matches CI:package.jsonengines)xvfbsopnpm test:integrationworks out of the boxpnpm install --frozen-lockfileon container creationxvfb-run -afor any headless environmentOutcome
One-click contributor environment that reproduces CI locally and removes a common source of first-run failures.