This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
fix: remove the socket client dependency and implement it directly in the SDK #723
Merged
+803
−73
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
Loading status checks…
… the SDK
Total Coverage: 89.18% Coverage Report
|
Total Coverage: 97.36% Coverage Report
|
vitorvargasdev
approved these changes
Jul 18, 2024
🎉 This PR is included in version 6.4.2-beta.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.4.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.5.0-lab.13 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When the clients deploy their applications in the Vercel client, the socket can't connect to the server, it's because the Vercel environment is a little different from the others.
The clients get this error:
Now the socket client and server is configured to run in the vercel too, avoiding the problems, and the clients can deploy and will be able to connect in the client too.