Allow no entry point

[ryanclark]

• This is a bugfix
• This is a code refactor
• This is a test update
• This is a typo fix
• This is a metadata update

For Bugs and Features; did you add new tests?

Yes

Motivation / Use-Case

Fixes this issue #1308

Allows for webpack-dev-server to run with no config or no configured entry point, keeping the behaviour consistent with the webpack compiler.

Additional Info

This should eventually be moved out of webpack-dev-server as we've currently got two places setting the default entry point (this and WebpackOptionsDefaulter).

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (webpack-4@9852a5f). Click here to learn what that means.
The diff coverage is 79.51%.

@@             Coverage Diff              @@
##             webpack-4    #1310   +/-   ##
============================================
  Coverage             ?   75.89%           
============================================
  Files                ?        9           
  Lines                ?      560           
  Branches             ?      146           
============================================
  Hits                 ?      425           
  Misses               ?      135           
  Partials             ?        0

Impacted Files	Coverage Δ
lib/OptionsValidationError.js	60.9% <100%> (ø)
lib/plugins.js	55.88% <55.88%> (ø)
lib/DevServer.js	71.71% <71.71%> (ø)
lib/features.js	80.43% <80.43%> (ø)
lib/server.js	80.55% <80.55%> (ø)
lib/util.js	82.5% <82.5%> (ø)
lib/app.js	87.09% <87.09%> (ø)
lib/proxy.js	95.55% <95.55%> (ø)

---

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 9852a5f...c99553a. Read the comment docs.

[ryanclark]

Seems like Codacy isn't reviewing this as it's going into next rather than master.

[SpaceK33z]

Thanks for your PR! Could you make it against webpack-4 branch? next is abandoned (see explanation).

I'll rename the next branch to make this more clear in the future.

[ryanclark]

@SpaceK33z all done!

[SpaceK33z]

Awesome, thanks!!

[TheLarkInn]

@SpaceK33z did we publish this yet onto the beta? If not lets do it!! Happy to do so if you are tight on time.

[ryanclark]

I believe it’s in 3.0.0-beta.2

…

On Fri, 23 Feb 2018 at 23:59, Sean Larkin ***@***.***> wrote: @SpaceK33z <https://github.com/spacek33z> did we publish this yet onto the beta? If not lets do it!! Happy to do so if you are tight on time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1310 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHjhvRRje7DatcGr3DliYcvoWNAE8Lc_ks5tX1D0gaJpZM4SJHLO> .

[SpaceK33z]

Yes it is in beta.2 already :).