-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
fix: include 'browserslist' in webTarget #2761
Conversation
Codecov Report
@@ Coverage Diff @@
## v4 #2761 +/- ##
=======================================
Coverage 93.04% 93.04%
=======================================
Files 39 39
Lines 1308 1308
Branches 348 348
=======================================
Hits 1217 1217
Misses 87 87
Partials 4 4
Continue to review full report at Codecov.
|
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.
It is not the best solution, but it is good as a temporary workaround
Seems |
It seems the
Here's the webpack 4's log:
Is the log of webpack 5 without that socket information expected? If it is, then we can no longer test the BTW, we have webpack 4 under |
CI on Node 6 and Node 8 failed because webpack 5 supports Node.js 10+. |
Yep, can you fix it? |
@evilebottnawi Are we going to support both webpack 4 and webpack 5 in webpack-dev-server v3? If yes, I guess we need to update the CI to test against both. |
I think yep, we need support two, not all developers migrate on webpack@5 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
According to the webpack docs, |
@leodr You are right here, it won't cover those cases as it's a naive fix at the moment. |
47fcbc7
to
4f4bccb
Compare
@chenxsan sorry for delay, can you switch on |
@evilebottnawi The fix is so naive that I was going to drop this PR. If you still want to accept it, I'll take care of it tomorrow. |
@chenxsan I want to merge it, we will improve more target logic in the future, this fix is enough |
44f8619
to
19b793f
Compare
4f7f58c
to
35ae034
Compare
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.
target can be array, so I think we need improve it too, anyway thanks for the PR
Maybe close this one in favor of #2841? Seems like @ylemkimon can fix it soon, hence no need to merge a workaround like this one. |
For Bugs and Features; did you add new tests?
Not yet.
Motivation / Use-Case
Close #2758
It's a naive fix, might need more research.
Breaking Changes
Additional Info