Patrick Steele-Idem

This module works by monkey-patching the internal `require('module').Module._nodeModulePaths` method to prepend additional directories: https://github.com/patrick-steele-idem/app-module-path-node/blob/97fc60947bcca6e194f549d0d374ef34a5eb49df/lib/index.js#L7-L17 You may want to consider using the more recent [require-self-ref](https://github.com/patrick-steele-idem/require-self-ref) module as an alternative. Both `app-module-path`...

Sounds like Webpack chose to use its own module resolving logic instead of using the the logic that Node.js provides internally. I don't think that was a good decision, but...

I haven't had a lot of time to look into this, but what are your thoughts on just using symbolic links in your project? That might be cleaner than further...

Hey @IngwiePhoenix, this module only changes how the Node.js module search paths are constructed. It doesn't change how modules are resolved which is what would be required for your use...

/cc @mlrawlings

/cc @mlrawlings Michael had done some work to revamp `browser-refresh`. Thoughts @mlrawlings ?

I don't use Windows so this is not something I can test. If you want to submit a PR to support Windows then feel free, but this is not something...

Labeling as an enhancement since this module is just using `require('child_process').spawn` directly and it is not a bug in this module that is preventing it from working on Windows.

On second thought, I don't think logic to resolve a Windows executable belongs in this module. It is probably better for the caller to pre-resolve the executable before using this...

I support the idea of making the `spawn` method configurable. I don't have a Windows machine or Windows VM set up, but if someone who does wants to contribute back...