chore(example/room-kit): bump react-native-video-plugin to ^2.0.0-alpha.0#1643
Conversation
…ha.0 Pairs with the video-plugin 2.0.0-alpha.0 release. Resolves the ERESOLVE peer-dep conflict between video-plugin 1.1.4 (which pins hms to <2.0.0) and the example app's local hms 2.0.0-alpha.1 — npm install was refusing to proceed without --legacy-peer-deps. With this bump, the example app and video-plugin agree on hms 2.x.
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
PR ReviewSummaryThis PR bumps Code Quality: ✅ LGTMThe changes are minimal and focused:
Issues & Concerns1. Inconsistent Version Across Codebase
|
…ha.0 (#1644) Follow-up to #1643. The previous PR bumped the **example app's** video-plugin to `^2.0.0-alpha.0`, but CI's `Link react-native-hms to room-kit` step runs from the **library directory** (`packages/react-native-room-kit/`), not the example. The library's own `devDependencies` and `additionalDependencies` still pinned video-plugin `1.1.4` / `1.1.0`, which peer-deps hms `<2.0.0` and re-triggered the same ERESOLVE conflict against the locally-packed hms `2.0.0-alpha.1` tarball. Two fields updated: - `devDependencies["@100mslive/react-native-video-plugin"]`: `1.1.4` → `^2.0.0-alpha.0` - `additionalDependencies["@100mslive/react-native-video-plugin"]`: `1.1.0` → `^2.0.0-alpha.0` `package-lock.json` regenerated accordingly. **Consumer impact:** none. `devDependencies` and the non-standard `additionalDependencies` are not installed when customers run `npm install @100mslive/react-native-room-kit`. This PR affects only our repo's CI + local dev setup.
Pairs with the newly published
@100mslive/[email protected](peer-dep on hms widened to^2.0.0-alpha.1).Fixes the ERESOLVE conflict that's been failing CI on the
BuildandBuild (New Architecture)workflows since #1642:After this bump:
2.0.0-alpha.0^2.0.0-alpha.1is satisfied by the example app's local hms tarballNo JS or native code changes — only
package.jsonand the regeneratedpackage-lock.json.