chore: use plugin support#4791
Conversation
… webpack-cli/package.json
🦋 Changeset detectedLatest commit: bc8faa7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4791 +/- ##
==========================================
+ Coverage 93.43% 93.46% +0.03%
==========================================
Files 14 14
Lines 5420 5513 +93
Branches 788 809 +21
==========================================
+ Hits 5064 5153 +89
- Misses 354 357 +3
- Partials 2 3 +1
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
I'm not sure if you want to support both dev-server 5 and 6 at the same time, with 6 being the one that has plugin support, or if you'd rather introduce this in a new major version for dev-server 6. |
…n invalid-schema test
…ility and signal handling
…ased on devServer version
bjohansebas
left a comment
There was a problem hiding this comment.
I think it's preferable to support dev-server 6 so it's easy to switch between versions, rather than releasing a new major version and making it more difficult to upgrade.
Summary
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