HMR does not work when specifying a port

[kentcdodds]

I recorded a loom to demonstrate the issue: https://www.loom.com/share/b9a88877d0a642cdbe305605212d1695

I tried a bunch of different combinations and it just appears that if you specify a PORT environment variable or use the -p flag, HMR will not work.

[pcattori]

Yea for unstable_dev, the PORT env var is vestigial. Should probably just ignore that env var for remix dev when using unstable_dev since its conflicting and causing weird stuff to happen.

Also adding better output for the dev server is on my list of things to do. Something like:

App server: localhost:4444
Dev server websocket port: 3001
Waiting for app server...

👆 to make it crystal clear what ports are being used and for what purpose.

That said, you should be able to use the --app-server-port and --port flags for remix dev (again, assuming unstable_dev is enabled). You probably don't care what port gets used for dev websocket, so just set --app-server-port=4444 to tell dev server where your app server is.

[kentcdodds]

That's great! I'll give that a shot next time I get in front of the keyboard. I guess we can leave this open as an issue to document this in --help and also to ignore the PORT env var or something. Thanks!

[pcattori]

Oh and I should mention that you can also set the app server port in remix.config.js:

module.exports = {
  unstable_dev: {
    appServerPort: 4444
  }
}

or via flag as mentioned previously. Your choice.

All configurable options are detailed in the release notes for v1.12.0, though still need to write up some better docs.

[kentcdodds]

Awesome. I've also added port: '' to that config so it selects a random port instead of using the environment variable PORT.

[github-actions]

🤖 Hello there,

We just published version v0.0.0-nightly-6295eb6-20230425 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!