In memory hot reloading for server side bundles.

Do you want to request a feature or report a bug?

What is the current behavior?
Currently there is no way to use memory-fs with a node compilation target while using hot module reloading.

If the current behavior is a bug, please provide the steps to reproduce.
Not a bug.

What is the expected behavior?
Ideally there would be a way to for webpack to automatically emit hot reload events if the bundle is running in the same process. Or provide a way to hook into webpack to provide the hot reload files to another process running the bundle.

If this is a feature request, what is motivation or use case for changing the behavior?
Currently I am stuck manually killing and reloading my node process. Ideally I would hot reload this as well since I am doing that for my browser build. The main issue with the current implementation (as far as I understand) with the node hot module reloading is that it is intrinsically tied to the actual file system which means my folder quickly fills up with hot reload files.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
webpack 2.x, node 7.x

Author: Fantashit

1 thought on “In memory hot reloading for server side bundles.

  1. This issue had no activity for at least half a year.

    It’s subject to automatic issue closing if there is no activity in the next 15 days.

Comments are closed.