pward123

I ran into a similar issue where I wanted to use react-css-modules and stylus. I ended up creating my own standalone webpack config. https://css-tricks.com/css-modules-part-2-getting-started/ has a decent walkthrough if you're...

The notification should go to the IP address of the guest and not the host (127.0.0.1), right? If I run the vagrant plugin, notification doesn't work. However, if I manually...

Ah, I didn't think about the port forwarding that's automatically configured by this plugin. For some reason the port forwarding setup is showing up in the parallels UI, but port...

I ended up creating a mashup of this plugin + vagrant-address. Instead of sending the notifications to a localhost port it sends them to the ip address that vagrant-address would...

Oh one other thing. Some watch type applications (like bazel-watcher in my case) don't catch the type of events that this plugin fires. I recommend something like iwatchnotify as a...

I also tried 5.22.1, setting log level to trace directly in the config file results in no logging at all

Looks like running in production mode and removing pretty `{ type: stdout, level: trace }` seems to get me some logging

I don't believe ibazel and webpack_dev_server work together. You just use webpack_dev_server. Here's how I'm using it. ``` load("@npm//http-server:index.bzl", "http_server") load("@npm//webpack-cli:index.bzl", "webpack_cli") load("@npm//webpack-dev-server:index.bzl", "webpack_dev_server") package(default_visibility = ["//visibility:public"]) NPM_PACKAGES = [...

In our case, we don't have any references to other targets in the workspace, only @npm// references. That may be why it's working for us without running ibazel. I've always...

Would you consider a PR for fb-watchman support with a fallback to filewatcher if watchman is not installed? If so, what version of node are you targeting? Package.json engines says...