Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for chrome launcher options #19

Open
electriquo opened this issue Sep 7, 2019 · 1 comment
Open

support for chrome launcher options #19

electriquo opened this issue Sep 7, 2019 · 1 comment

Comments

@electriquo
Copy link

electriquo commented Sep 7, 2019

there is the need to configure webpack dev-server to use https in order to work with service worker. 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 which is utilised by lighthouse.

  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)?
@electriquo
Copy link
Author

anyone?

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

No branches or pull requests

1 participant