Repository navigation
chore: add expo-device-hub dev tools plugin - #148
Merged
Merged
Conversation
Install expo-device-hub 0.18.0 as a devDependency and document how to open Device Hub during local development. Co-authored-by: prdHugo <HugoPerard@users.noreply.github.com>
|
π Expo preview is ready!
|
pnpm allowBuilds for node-datachannel so prebuild-install fetches the N-API binary at install time. Clarify README URL/host and Android SDK tools. Co-authored-by: prdHugo <HugoPerard@users.noreply.github.com>
Rely on Device Hub lazy prebuild-install on first Android WebRTC use; pnpm default already blocks the install script. Co-authored-by: prdHugo <HugoPerard@users.noreply.github.com>
This file contains hidden or 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.
Summary
Adds expo-device-hub as a dev-only Expo DevTools plugin so simulators and emulators can be streamed and controlled from the browser during local development.
Changes
expo-device-hub@0.18.0todevDependencies(installed viapnpm exec expo install expo-device-hub -- -D, exact pin).pnpm dev:client/expo start, terminal URL, standalone CLI, platform requirements).Lockfile size
The
pnpm-lock.yamldiff is large mainly because addingexpo-device-hubpulls in a new dependency subtree, and pnpm also normalizes many existing lockfile entries (dropping the(supports-color@8.1.1)peer suffix on ~190 packages). No intentional version bumps to existing app dependencies.Notes
expo-module.config.jsononly registers thedevtoolsplatform (no iOS/Android config plugin). It is not linked into release builds.minimumReleaseAge: No extra excludes were required;expo-device-hubis already covered by the existingexpo-*pattern inpnpm-workspace.yaml.node-datachannel(pulled by expo-device-hubβs serve-emu path) is not part of the React Native binary; pnpm does not run its install script by default, and Device Hub can fetch the prebuilt N-API binary on first Android WebRTC use.Verification
pnpm install --frozen-lockfilepnpm lint:tspnpm lintexpo startprints an Expo Device Hub URL (e.g.http://<dev-server-host>:8081/_expo/plugins/expo-device-hub).