Update broke my workflow about browserify-hmr HOT 4 CLOSED

You need to use the h/hostname option. You'll probably want to use -h 0.0.0.0 to listen on all addresses instead of just localhost. This was a breaking change in 0.3.0. (This project is following semver. Major version updates, and minor version updates before 1.0.0 may contain breaking changes.)

Previously, the hostname and port were automatically inferred from the u/url option, but this was restrictive and didn't allow people to make the socket server listen on an address (like 0.0.0.0) that was different from what the client accessed. (#4)

from browserify-hmr.

Not sure if I understand you correct. As you can see above, I'm using

 "scripts": {
    "watch": "watchify source/index.js -p [ browserify-hmr -u http://$(my-local-ip):3123 ] -p ghostmodeify -t babelify -o public/browser/bundle.js -dv"
  }

I now updated to 0.3.1 again and changed my script to

 "scripts": {
    "watch": "watchify source/index.js -p [ browserify-hmr -h $(my-local-ip) ] -p ghostmodeify -t babelify -o public/browser/bundle.js -dv"
  }

but it's not working. If i switch $(my-local-ip) for 0.0.0.0 its working, but the problem is, that it breaks my workflow developing a cordova app on my mobile phone, because it needs to connect to the server that runs on my notebook instead of searching on localhost, so it was really nice to be able to use my-local-ip instead.

from browserify-hmr.

You still need the -u option. The -u option controls what URL is written into the bundle. The -h option controls what address the browserify-hmr socket server listens on. Previous versions automatically guessed the hostname based on the url, but 0.3.0 split them into separate options.

from browserify-hmr.

oh, ok. i see. I'll try that. thx

from browserify-hmr.