-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
cli(fr): add --fraggle-rock flag #12805
Conversation
const fraggleRock = require('../lighthouse-core/fraggle-rock/api.js'); | ||
const puppeteer = require('puppeteer'); | ||
// @ts-expect-error - FIXME: lighthouse-logger is greedy and takes over `debug` for all packages | ||
require('debug').enable('-puppeteer:*'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please pull up this require to reduce an extra complication when automating the conversion to ESM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh is that happening imminently? I don't want this line to exist for more than a week (PR already in progress to make it unnecessary)
If you're referring to puppeteer, I was hoping to avoid injecting puppeteer into the default dependencies for an experimental flag due to the extra postinstall hooks. const puppeteer = await import('puppeteer')
should be OK, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh is that happening imminently?
No, just a mechanical code review suggestion I have these days when I see require
:)
const puppeteer = await import('puppeteer') should be OK, right?
Yeah
Summary
Happy to add whatever public caveats others think is wise to minimize accidental usage at this stage (currently just
[EXPERIMENTAL]
on the CLI flag). Hopefully this gets us more internal usage, I know I'll be trying it out a bit more :) It's not at complete parity yet, but the basic default usage should be working at this point.Next steps:
lighthouse-logger
to avoid stomping on other packages debug misc: add prefix to lighthouse-logger debug scope #12806Related Issues/PRs
ref #11313