Skip to content

docs: state the Playwright prerequisite for the e2e suite - #310

Merged
cf-pages merged 1 commit into
mainfrom
claude/review-mergeable-prs-itwtwy
Jul 25, 2026
Merged

cf-pages merged 1 commit into
mainfrom
claude/review-mergeable-prs-itwtwy

Conversation

@cf-pages

Copy link
Copy Markdown
Owner

Follow-up to #309. The end-to-end suite was committed without documenting that it needs Playwright, so anyone following the README would hit a raw MODULE_NOT_FOUND stack trace.

Playwright stays out of the project dependencies deliberately — adding it would put a browser download in every contributor's npm install for a suite that is optional and not run in CI. So:

  • README (en/zh) documents the one-time install: npm install --no-save playwright && npx playwright install chromium
  • test/e2e/homepage.js catches the missing module and prints that exact command instead of a stack trace

Verified by temporarily removing the module and confirming the message appears.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Lo4BJZPgVbFcUk5RTZkvjf


Generated by Claude Code

The suite was committed without saying it needs Playwright, so following
the README would fail with a raw module-not-found error. Playwright stays
out of the project dependencies on purpose — it would add a browser
download to every contributor's npm install for an optional suite — so
document the one-time install instead, and have the runner print that
command rather than a stack trace when the module is absent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Lo4BJZPgVbFcUk5RTZkvjf
@cf-pages
cf-pages merged commit 76e2e26 into main Jul 25, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants