fix: bump chromium-bidi to a version that does not declare mitt as a peer dependency #9701
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
OrKoN
force-pushed
the
orkon/update-chromium-bidi
branch
from
0a6e9fa
to
11a6a4d
Compare
Lightning00Blade
approved these changes
Feb 17, 2023
OrKoN
force-pushed
the
orkon/update-chromium-bidi
branch
from
11a6a4d
to
d6752bd
Compare
OrKoN
changed the title
This was referenced Feb 17, 2023
Closed
Closed
Closed
Closed
Merged
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.
The release makes mitt a proper dependency so we don't need to have chromium-bidi as an optional peer dependency that proved to not work well with some projects such as Webpack.