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
Feature request summary
plugin supports scope npm package
like this:
NODE_PATH=.. yarn lighthouse http://127.0.0.1:5502/index.html --plugins=@xxx/lighthouse-plugin-demo --only-categories=@xxx/lighthouse-plugin-demo --view
What is the motivation or use case for changing this?
Our company generates some private npm packages by itself, with a scope prefix, hoping that the plugin can support the loading of private packages
How is this beneficial to Lighthouse? Support the loading of company private packages
The text was updated successfully, but these errors were encountered:
Feature request summary
plugin supports scope npm package
like this:
What is the motivation or use case for changing this?
Our company generates some private npm packages by itself, with a scope prefix, hoping that the plugin can support the loading of private packages
How is this beneficial to Lighthouse?
Support the loading of company private packages
The text was updated successfully, but these errors were encountered: