M Behzad
M Behzad
when running the tests locally with the same node version (v8.9.1) as in the travis error. everything passes without any issues. (on a 64x windows machine) 🤔
i run the tests locally in a docker container (linux, node v8.9.1) and they run without errors. I couldn't find any wrong file names in the code and I don't...
tests are passing now
Hi @csentis, i would say Webpack Monitor has two types of features, - capturing stats like number of chunks/assets, their sizes, dependency graph, ... and showing their changes over time,...
Hi @roachjc, i know the webpack monitor is meant to track releases / production builds stats. But i think there is legit use case for using it in a watch...
Hi @roachjc , yes you have a good point. I had a happy case in mind where dev and prod settings are similar. I think an option to "capture" the...
Hi @dimitarnestorov, you are right, webpack monitor is not ment to be used in a watch mode: (from #48): > Typically you'd insert webpack monitor as a plugin on your...
@dimitarnestorov , you said supporting a watch mode would be your feature request. What would be your use case, or what behavior would you expect? - with the current default...
Hi @silvestrijonathan, could you share your webpack + babel config here?
Hi @melunar, it sounds like webpack-monitor is already running, or the `8081` port is used by another application. For example if the webpack-monitor is in your webpack configuration which is...