Skip to content

support for chrome launcher options #19

@electriquo

Description

@electriquo

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)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions