Update webpack-dev-server utils path

[daviferreira]

Q	A
Bug fix?	no
Breaking change?	yes
New feature?	no
Deprecations?	no
Tests added?	no
Docs updated?	no
Fixed tickets	comma-separated list of tickets fixed by the PR, if any
License	MIT

webpack-dev-server util directory was renamed to utils on v3.1.7

webpack/webpack-dev-server#1465

[jsf-clabot]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #166 into master will decrease coverage by 0.29%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #166     +/-   ##
=========================================
- Coverage   64.48%   64.18%   -0.3%     
=========================================
  Files           8        8             
  Lines         214      215      +1     
  Branches       53       53             
=========================================
  Hits          138      138             
- Misses         62       63      +1     
  Partials       14       14

Impacted Files	Coverage Δ
tasks/webpack-dev-server.js	13.72% <0%> (-0.28%)	⬇️

---

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 1162bec...05bafac. Read the comment docs.

[ghost]

I would say it should try both paths. Its sad this change was done in a patch-version bump of webpack-dev-server

[TheSpyder]

The utils folder is private API, nobody should have any expectation of internal API compatibility. The moment you start doing require('package/<anything>') you're bypassing the main field in package.json and taking a risk.

I logged an issue with webpack-dev-server yesterday to check, and confirmed this - the recommendation to fix the error is to have a try/catch that supports both paths.
webpack/webpack-dev-server#1483

[danez]

Thanks.

[ghost]

@TheSpyder You are right. The actual question is: What official API could this package use in order to prevent this from happening in the future. Seems to me that this fix going to break again, when someone decides to refactor webpack-dev-server.