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

core: remove budgets #15950

Merged
merged 3 commits into from
Apr 17, 2024
Merged

core: remove budgets #15950

merged 3 commits into from
Apr 17, 2024

Conversation

connorjclark
Copy link
Collaborator

closes #15203

core/config/default-config.js Show resolved Hide resolved
@@ -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 () => {
Copy link
Member

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.

@@ -13,37 +13,6 @@ const budgetedConfig = {
extends: 'lighthouse:default',
settings: {
throttlingMethod: 'devtools',
budgets: [{
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider dropping budgets from lighthouse core
3 participants