
Security News
MCP Community Begins Work on Official MCP Metaregistry
The MCP community is launching an official registry to standardize AI tool discovery and let agents dynamically find and install MCP servers.
@config-plugins/react-native-webrtc
Advanced tools
Config plugin to setup react-native-webrtc on prebuild
Config plugin to auto-configure react-native-webrtc
when the native code is generated (npx expo prebuild
). Upstream PR.
Ensure you use versions that work together!
expo | react-native-webrtc | @config-plugins/react-native-webrtc |
---|---|---|
52.0.0 | 124.0.4 | 10.0.0 |
51.0.0 | 118.0.7 | 9.0.0 |
50.0.0 | 118.0.1 | 8.0.0 |
49.0.0 | 111.0.3 | 7.0.0 |
48.0.0 | 106.0.6 | 6.0.0 |
47.0.0 | 1.106.1 | 5.0.0 |
46.0.0 | 1.100.0 | 4.0.0 |
45.0.0 | 1.100.0 | 3.0.0 |
44.0.0 | 1.92.2 | 2.0.0 |
43.0.0 | 1.92.2 | 1.0.0 |
Expo SDK 42 uses
react-native@0.63
which doesn't work withreact-native-webrtc
, specifically iOS production builds fail. Meaning this package is only supported for Expo SDK +43.
This package cannot be used in the "Expo Go" app because it requires custom native code. First install the package with yarn, npm, or
npx expo install
.
npx expo install react-native-webrtc @config-plugins/react-native-webrtc
After installing this npm package, add the config plugin to the plugins
array of your app.json
or app.config.js
:
{
"plugins": ["@config-plugins/react-native-webrtc"]
}
Next, rebuild your app as described in the "Adding custom native code" guide.
SDK 50 and greater.
React Native uses event-target-shim@5
which is not compatible with react-native-webrtc
's dependency on event-target-shim@6
. To fix this, you may need to add a redirection in your metro.config.js
file:
// metro.config.js
// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require("expo/metro-config");
const resolveFrom = require("resolve-from");
/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);
config.resolver.resolveRequest = (context, moduleName, platform) => {
if (
// If the bundle is resolving "event-target-shim" from a module that is part of "react-native-webrtc".
moduleName.startsWith("event-target-shim") &&
context.originModulePath.includes("react-native-webrtc")
) {
// Resolve event-target-shim relative to the react-native-webrtc package to use v6.
// React Native requires v5 which is not compatible with react-native-webrtc.
const eventTargetShimPath = resolveFrom(
context.originModulePath,
moduleName
);
return {
filePath: eventTargetShimPath,
type: "sourceFile",
};
}
// Ensure you call the default resolver.
return context.resolveRequest(context, moduleName, platform);
};
module.exports = config;
The plugin provides props for extra customization. Every time you change the props or plugins, you'll need to rebuild (and prebuild
) the native app. If no extra properties are added, defaults will be used.
cameraPermission
(string): Sets the iOS NSCameraUsageDescription
permission message to the Info.plist
. Defaults to Allow $(PRODUCT_NAME) to access your camera
.microphonePermission
(string): Sets the iOS NSMicrophoneUsageDescription
permission message to the Info.plist
. Defaults to Allow $(PRODUCT_NAME) to access your microphone
.app.config.js
export default {
plugins: [
[
"@config-plugins/react-native-webrtc",
{
cameraPermission: "Allow $(PRODUCT_NAME) to access your camera",
microphonePermission: "Allow $(PRODUCT_NAME) to access your microphone",
},
],
],
};
gradle.properties
: android.enableDexingArtifactTransform.desugaring=false
and the minimum deployment target is changed to 24
(from 21
) which may break other packages in your app!For bare workflow projects, you can follow the manual setup guides:
FAQs
Config plugin to setup react-native-webrtc on prebuild
The npm package @config-plugins/react-native-webrtc receives a total of 7,696 weekly downloads. As such, @config-plugins/react-native-webrtc popularity was classified as popular.
We found that @config-plugins/react-native-webrtc demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The MCP community is launching an official registry to standardize AI tool discovery and let agents dynamically find and install MCP servers.
Research
Security News
Socket uncovers an npm Trojan stealing crypto wallets and BullX credentials via obfuscated code and Telegram exfiltration.
Research
Security News
Malicious npm packages posing as developer tools target macOS Cursor IDE users, stealing credentials and modifying files to gain persistent backdoor access.