Webpack watch mode is broken for me. When using single configuration, it compiles only once. With multiple configurations, it complains that compiler.watchings doesn't exist.
It seems this was introduced with 95ab0896973fc14f21307ff6f94655c0c0327bbf. This commit changed the way the compilation is started from running webpack with a callback to calling the run method separately.
Calling webpack with a callback called run or watch automatically and returned Compiler, MultiCompiler, Watching or MultiWatching.
Now, when calling webpack without the callback, it always returns Compiler or MultiCompiler, but webpack-stream still expects to get MultiWatching when runing in the watch mode with multiple configurations.
This PR removes special cases for [Multi]Watching and calls watch instead of run method when appropriate.
Webpack watch mode is broken for me. When using single configuration, it compiles only once. With multiple configurations, it complains that
compiler.watchings
doesn't exist.It seems this was introduced with 95ab0896973fc14f21307ff6f94655c0c0327bbf. This commit changed the way the compilation is started from running
webpack
with a callback to calling therun
method separately.Calling
webpack
with a callback calledrun
orwatch
automatically and returnedCompiler
,MultiCompiler
,Watching
orMultiWatching
.Now, when calling
webpack
without the callback, it always returnsCompiler
orMultiCompiler
, butwebpack-stream
still expects to getMultiWatching
when runing in the watch mode with multiple configurations.This PR removes special cases for
[Multi]Watching
and callswatch
instead ofrun
method when appropriate.