Skip to content

docs: document the setup with Lighthouse and with user-flow - #20

Merged
ChristopherPHolder merged 1 commit into
mainfrom
t3/document-lighthouse-user-flow-setup
Nov 14, 2026
Merged

ChristopherPHolder merged 1 commit into
mainfrom
t3/document-lighthouse-user-flow-setup

Conversation

@ChristopherPHolder

Copy link
Copy Markdown
Collaborator

Closes #19

The docs site had one Usage page that set the package up with Lighthouse and mentioned user-flow in a short section at the end. Each setup now has its own page.

Pages

  • Set up with Lighthouse (/docs/getting-started/lighthouse): install, the flow script, how to run it. This is the old Usage page without the user-flow and result sections.
  • Set up with user-flow (/docs/getting-started/user-flow): install, .user-flowrc.json, the flow file, npx user-flow collect and the settings for every flow. It links to the user-flow docs for recordings and the rest of the CLI.
  • Reading the result (/docs/guides/results): the result section of the old Usage page, since it applies to both setups.
  • Introduction ends with the two setups and links to both.

Also

  • /docs/getting-started/usage redirects to the Lighthouse page.
  • "Get started" on the landing page goes to the introduction, where the two setups split.
  • Throttling links to both setup pages and to the project settings of user-flow.
  • Troubleshooting has a row for Could not find Chrome: npm 11 and pnpm skip Puppeteer's install script, so Chrome isn't downloaded on install.

Tested

I ran the code of both pages against the e2e fixture app, each in a fresh project installed with the command of its page:

  • node flow.mjs: a page load and two soft navigations, no audit errors or run warnings.
  • npx user-flow collect with the .user-flowrc.json and flow file of the page: the same three steps.
  • The same flow without step options and with throttlingMethod in .user-flowrc.json: every step runs with DevTools throttling.

pnpm nx run-many -t lint typecheck build -p docs passes.

The Usage page set the package up with Lighthouse and mentioned user-flow in a short section. Each setup now has its own page, from install to report. The introduction links to both, and reading the result has its own page since it applies to both.

The old Usage URL redirects to the Lighthouse page.

Closes #19
@ChristopherPHolder
ChristopherPHolder merged commit c7b845f into main Nov 14, 2026
1 check 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.

docs: document the two setups, with Lighthouse and with user-flow

1 participant