push-based/Lighthouse User Flow CI Action
Audit URL's using Lighthouse user flow and test performance within PR's
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| commentId | A custom id to identify a comments in a PR | no | user flow summary report |
| onlyComments | No execution of userflow. Just creation of the comments in the PR. | no | off |
| rcPath | Path to a UFCI user-flowrc.json file | no | .user-flowrc.json |
| verbose | Verbose logging flag ("on" or "off") | no | off |
| url | URL to analyze | no | — |
| ufPath | Path to user-flow file or folder containing user-flow files to run. (`*.uf.ts` or `*.uf.js`) | no | — |
| configPath | Path to the lighthouse `config.json` file | no | — |
| serveCommand | Runs a npm script to serve the target app. This has to be used in combination with `--awaitServeStdout` | no | — |
| awaitServeStdout | Waits for stdout from the serve command to start collecting user-flows | no | — |
| dryRun | Faster runs due to dummy results for reports ("on" or "off") | no | off |
| format | Format of the creates reports ( `html`, `json`, `md`, `stdout`) | no | — |
| outPath | output folder for the user-flow reports | no | — |
| budgetPath | Path to the lighthouse `budget.json` file | no | — |
Outputs
no outputs