You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are all your remix dependencies & dev-dependencies using the same version?
Yes
Steps to Reproduce
Try to set the websocket port via the future.unstable_dev.websocketPort config option.
Expected Behavior
The browser connects to the specified websocket port.
Actual Behavior
The browser still tries to connects to the default port 3001, ignoring the config.
This is because there is inconsistency in the source code. Some files refer to the config key as websocketPort (as documented in release notes), while others refer to it as webSocketPort (with an uppercase 'S' for Socket). I think this inconsistency was introduced in 1.16.1, as if memory serves it was working in 1.16.0.
The text was updated successfully, but these errors were encountered:
We just published version v0.0.0-nightly-33cc4c0-20230525 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!
We just published version 1.17.0-pre.0 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!
What version of Remix are you using?
1.16.1
Are all your remix dependencies & dev-dependencies using the same version?
Steps to Reproduce
Try to set the websocket port via the
future.unstable_dev.websocketPort
config option.Expected Behavior
The browser connects to the specified websocket port.
Actual Behavior
The browser still tries to connects to the default port 3001, ignoring the config.
This is because there is inconsistency in the source code. Some files refer to the config key as
websocketPort
(as documented in release notes), while others refer to it aswebSocketPort
(with an uppercase 'S' for Socket). I think this inconsistency was introduced in 1.16.1, as if memory serves it was working in 1.16.0.The text was updated successfully, but these errors were encountered: