webpack-cli
webpack-cli copied to clipboard
feat: Interactive Plugin
Different from interactive
at #586: This PR just adds support for interactive output mode.
What kind of change does this PR introduce? Feature
Did you add tests for your changes?
If relevant, did you update the documentation? Not applicable
Summary
There are two output modes for --watch
and webpack serve
, standard and interactive.
Standard is already supported. This PR aims to implement that.
Does this PR introduce a breaking change? No
Other information /cc @alexander-akait
Codecov Report
Merging #3243 (e6835e3) into master (748ae9e) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #3243 +/- ##
=======================================
Coverage 92.08% 92.08%
=======================================
Files 23 23
Lines 1731 1731
Branches 519 519
=======================================
Hits 1594 1594
Misses 137 137
Impacted Files | Coverage Δ | |
---|---|---|
packages/webpack-cli/src/webpack-cli.ts | 93.95% <ø> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 5034913...e6835e3. Read the comment docs.
This is just empty code though....
Yeah, I know 😆 . See #1796 closing comment for more info.
Yes, let's finish it, although perhaps we should first do major release:
- drop node v12
- drop webpack-dev-server v3
- update deps (there is possible without big changes)
Yes, let's finish it, although perhaps we should first do major release:
- drop node v12
- drop webpack-dev-server v3
- update deps (there is possible without big changes)
Okay, will do. Should node version 10 be removed too?
Sorry for losing your time, but let's close it due https://github.com/webpack/webpack-cli/issues/586#issuecomment-1528836367
In the future, we should study better and deeper the issues of what we should develop or not, in order not to get into such situations, once again I deeply apologize