Allow version range from @livekit/protocol dependency
#1356
+1
−1
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
This should ensure when installing it along with other SDKs (such as `livekit-server-sdk`) to always resolve to a common compatible version without having to dedupe the dependencies.
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.
I realized when migrating to v2 that yarn resolved two separate versions of
@livekit/protocol.This should ensure when installing it along with other SDKs (such as
livekit-server-sdk) to always resolve to a common compatible version without having to dedupe the dependencies.It's just a suggestion, it may be the case that the livekit team has a very specific reason for pinning the version in this js sdk?