Support for hot reloading about webpackmonitor

[jeffkamo]

I'm having the same issue. Is there a work around?

[roachjc]

Hey @jaepd and @jaepd. Thank you for getting in touch!

Yeah it won't work on hot reloading I'm afraid, and nor should it want to. But would be good to handle this a bit better than erroring ... so sorry for that!

As for a workaround, don't include it in the webpack config that runs hot reload. The idea is that wpm is really only worth using for production builds where your optimization will take effect and builds will only take place periodically. It's just to keep a record of your proper builds and a mechanism to refer to that record, rather than something you're going to be looking at as you write your project and while you're using hot reload.

Hope that is of some help!

Thank you for your feedback! Defo will look at handling this more 'gracefully' 😬

[jeffkamo]

That makes a lot of sense! Moving the plugin to our production webpack config did the trick.

Thanks for clarifying!

[jadennnn]

Hey thanks for confirming & yes it would be nice to see a little message :)

[DanielRuf]

production webpack config

This makes not much sense in production mode.

[DanielRuf]

Watch mode should be supported. Running this in production on a server is not a good idea.

[DanielRuf]

At least it seems the data is not reloaded. I started two webpack instances. One launches wpm and the other doesn't but writes / should write to the file.

But the client does not reload the new data. Even if I manually edit the json file and reload in the browser it does not work. And I guess this is the root problem.

See how the developers of jarvis do it
https://github.com/zouhir/jarvis/search?utf8=%E2%9C%93&q=hot&type=