search

GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.
https://developer.chrome.com/docs/lighthouse/overview/
Apache License 2.0
28.23k stars 9.35k forks source link

allow directory as input to --output-path #7408

Open brendankenny opened 5 years ago

brendankenny commented 5 years ago

was #4369, but we didn't move on it and it became obsolete. Concept still seems good, though we might end up taking a different tactic.

jjt commented 5 years ago

Here's my current simple stupid workaround in the meantime 🙃 

#!/bin/bash
mkdir -p .lighthouse-reports
cd .lighthouse-reports

lighthouse #...
alexcroox commented 5 years ago

What is the solution currently to specifying a different output folder but maintaining the dynamic domain and date of reporting being added to the filename?

Currently if you specify an output path the filename has to be static, overwriting the previous report?

e.g npx lighthouse https://alexcrooks.me --output-path=./tests/lighthouse/report.html

patrickhulce commented 5 years ago

@alexcroox you can change your cwd like the example in https://github.com/GoogleChrome/lighthouse/issues/7408#issuecomment-476306740.

alexcroox commented 5 years ago

Ah yes I could just cd into the directory as part of the command. Thanks!