chore: update webpack-dev-middleware#5654
Merged
bjohansebas merged 2 commits intonextfrom Mar 30, 2026
Merged
Conversation
Member
|
@bjohansebas let's fix tests, I think we need change some part of code here |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next #5654 +/- ##
==========================================
+ Coverage 83.54% 83.57% +0.03%
==========================================
Files 11 11
Lines 1920 1924 +4
Branches 706 707 +1
==========================================
+ Hits 1604 1608 +4
Misses 283 283
Partials 33 33 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
alexander-akait
approved these changes
Mar 30, 2026
Member
alexander-akait
left a comment
There was a problem hiding this comment.
Feel free to merge when will be green
This file contains hidden or 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
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.
Summary
A separate PR in case there are other changes to make,though as far as I know there aren’t,but it’s better to do it separately so it doesn’t affect the other PRs
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI