fix: Extended budgets so that npm builds successfully #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DavidCroftDKFZ
changed the title
torbrenner
force-pushed
the
budget_extensions
branch
from
e02e62c
to
0e9406a
Compare
I extended both the warning and error budgets, to stop warnings from being printed and to enable the npm build to continue to completion.
torbrenner
force-pushed
the
budget_extensions
branch
from
0e9406a
to
974c4a0
Compare
torbrenner
approved these changes
Sep 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: I extended both the warning and error budgets, to stop warnings from being printed and to enable the npm build to continue to completion.