Socket server locally #3063
Merged
Socket server locally #3063
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
🤖 Generated by Copilot at 9bd1ba4
Updated the app's environment and socket configuration. Added a new variable to
.env.exampleandpackage.jsonto set the socket server host. Modified theisDevEnvconstant inconfig/constants.tsto useNODE_ENVas a fallback.WHY
So it turns out that Next 14 FIXED the issue with socket.io: vercel/next.js#49334. However, I think it's worth keeping the separation because it is a closer mirror to production and testing. I believe we can actually delete the socket.io endpoint that Next.js serves, but i'll save that for another PR