-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
devServerPort
not set on fresh install with "Just the basics" & "Express Server" target
#3237
Comments
same here, but with netlify... |
This is because in #3206 the script obtains a random available port if the environment variable isn't set - it's undefined for this template as Adding "devServerPort": 8002 in the remix.config.js of this (and other) templates should fix the problem. |
Yes, I've noticed the same thing and commented here as to why it's happening and a couple of solutions. One as you noted is to specify the |
It seems like this is still an issue. Anyways we can add back in the default devServerPort? |
I'm running into the same issue while going through the Remix app tutorial. Setting |
@acurry had the same issue. looks like its broken in v2. setting |
@sepbot That worked! Thanks! |
What version of Remix are you using?
v1.5.1
Steps to Reproduce
create-remix@latest
install, select "Just the basics" for app type and "Express Server" for target.npm run dev
http://localhost:3000
with dev tools open.WebSocket connection to 'ws://localhost:8002/socket' failed:
&Remix dev asset server web socket error:
messages in console.Terminal log:
Expected Behavior
No errors in console &
@remix/remix-dev
websocket connection + LiveReload to work as expected.Note: This can be resolved by explicitly setting
"devServerPort": 8002
inremix.config.js
but the documentation (and functionality in prior versions) indicate that8002
should be the defaultdevServerPort
value.Actual Behavior
WebSocket connection to 'ws://localhost:8002/socket' failed:
&Remix dev asset server web socket error:
messages in browser console (see screenshot).The text was updated successfully, but these errors were encountered: