-
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
core: remove budgets #15950
core: remove budgets #15950
Conversation
@@ -64,20 +64,6 @@ describe('Performance: Resource summary audit', () => { | |||
expect(thirdParty.transferSize).toBe(145); | |||
expect(thirdParty.requestCount).toBe(3); | |||
}); | |||
|
|||
it('uses firstPartyHostnames if provided', async () => { |
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.
FWIW this does seem like a feature we are losing with this PR. That being said, it's only used in this one hidden audit and not anywhere else so I still think it's fine.
build/test/page-functions-test-case-computeBenchmarkIndex-out.js.map
Outdated
Show resolved
Hide resolved
@@ -13,37 +13,6 @@ const budgetedConfig = { | |||
extends: 'lighthouse:default', | |||
settings: { | |||
throttlingMethod: 'devtools', | |||
budgets: [{ |
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.
nit: this is called budgetedConfig
here and in update-report-fixtures.js
. Could we just call it sampleConfig
?
closes #15203