addyosmani / addyosmani/webpack-lighthouse-plugin

support for chrome launcher options

Abierto
#19 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
294
Forks
12
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

there is the need to [configure webpack dev-server to use https][1] in order to work with [service worker][2]. webpack dev-server can be configured to serve self-signed certificate. as a result, chromium needs to launched with `--ignore-certificate-errors` and `--unsafely-treat-insecure-origin-as-secure=https://localhost:8080` arguments, but there is no straightforward way to provide chromium arguments to lighthouse-plugin.

[chrome-launcher options supports `chromeFlags`][3] which is utilised by [lighthouse][4].

1. is there any way to provide the arguments for chrome-launcher?
2. is there any way to control the plugin execution only when the webpack dev-server kicks in and not for webpack in general (for instance, not to run when only bundeling takes place)?

[1]: https://webpack.js.org/configuration/dev-server/#devserverhttps
[2]: https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers#Setting_up_to_play_with_service_workers
[3]: https://github.com/GoogleChrome/chrome-launcher#launchopts
[4]: https://github.com/GoogleChrome/lighthouse/blob/master/docs/readme.md#using-programmatically

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.