“Built-in mobile libraries are listed below. You can add additional libraries; if your version conflicts with one we ship, ours takes precedence.” is what the shared technical tab says, but I can’t figure out how to add my own library?
Have you ever heard of mobile plugins? That way..
I am on the plugin editor…that’s where it says that. I don’t want to use someone’s plugin (because my integration doesn’t even have one), how can I add a custom library to my plugin?
Not sure why it says “..You can add additional libraries..” but bubble devs are still in the works of adding third party libraries.
The following libraries are currently supported:
"@bbob/preset-react": "^4.2.0", "@bbob/reagire": "^4.2.0", "@expo/metro-runtime": "~55.0.6", "@gorhom/bottom-sheet": "^5.2.8", "@gorhom/portale": "^1.0.14", "@microsoft/react-native-clarity": "^4.2.2", "@react-native-community/audio-toolkit": "^2.0.3", "@react-native-community/datetimepicker": "8.6.0", "@react-native-community/netinfo": "11.5.2", "@react-navigation/bottom-tabs": "^7.8.9", "@react-navigation/elementi": "^2.8.5", "@react-navigation/native": "^7.1.22", "@react-navigation/native-stack": "^7.8.3", "@sentry/react-native": "~7.11.0", "@shopify/flash-list": "2.0.2", "browserify-zlib": "^0.2.0", "crypto-browserify": "^3.12.0", "expo": "~55.0.7", "expose-asset": "~55.0.9", "expo-audio": "~55.0.14", "expo-auth-session": "~55.0.8", "esposizione-sfocatura": "~55.0.10", "expo-camera": "~55.0.10", "Expo-clipboard": "~55.0.9", "expo-costanti": "~55.0.8", "expo-crypto": "~55.0.10", "expo-document-picker": "~55.0.9", "expo-file-system": "~55.0.11", "expo-iap": "^3.4.10", "immagine dell'esposizione": "~55.0.6", "expo-image-manipulator": "~55.0.11", "expo-image-picker": "~55.0.13", "expo-lineare-gradiente": "~55.0.9", "expo-linking": "~55.0.7", "posizione-esposizione": "~55.1.3", "expo-media-library": "~55.0.10", "notifiche di esposizione": "~55.0.13", "Expo-secure-store": "~55.0.9", "esposizione-condivisione": "~55.0.19", "expo-splash-screen": "~55.0.11", "expo-status-bar": "~55.0.4", "Aggiornamenti dell'esposizione": "~55.0.14", "video-expo": "~55.0.11", "expo-web-browser": "~55.0.10", "codifica del testo veloce": "^1.0.6", "percorso-browserify": "^1.0.1", "reagire": "19.2.0", "react-dom": "19.2.0", "reazione-nativa": "0.83.2", "react-native-gesture-handler": "~2.30.0", "reagire-nativo-localizzare": "^3.5.1", "mappe-native-react": "1.27.2", "reazione-nativa-mmkv": "^4.2.0", "react-native-modal-date-time-picker": "^18.0.0", "moduli-nitro-nativi-react": "^0.35.0", "react-native-reanimated": "4.2.1", "react-native-redash": "^18.1.1", "reagire-nativo-area-sicura-contesto": "^5.6.2", "react-native-screens": "~4.23.0", "react-native-svg": "15.15.3", "react-native-web": "~0.21.0", "react-native-webview": "13.16.0", "react-native-worklets": "0.7.2", "rn-fetch-blob": "^0.12.0", "stream-browserify": "^3.0.0"
For the rest I suggest you consult Bubble Bot instead of the forum..
Yeah, I don’t think you know what “my own library” means…I already saw this. That’s where I got
The question was about adding a custom library, obv. it’s via a plugin, this is the plugin builders subsection to your first response.
Idk what all your attitude comes from?
Seems like the copy is getting ahead of ourselves a little - this is functionality thats currently only available through a feature flag. We expect to open this up to all plugin developers early september. In the meantime, feel free to reach out if you want alpha access.
@nick.carroll That would be great! I sent you a PM. The third-party libraries would be a must for me to build using Bubble for native mobile.
I’ve had confirmation from Bubble not so long ago that this is being worked on, but not yet available to us. Hopefully it will happen soon though.
Ah okay, I figured esp. with the copy saying so. Yes, super hopeful on it! I am blocked until it is ready for what I’m looking to achieve with the mobile builder.
What’s the library called? You might be able to import it through other means.
Knock Notifications: Knock React Native SDK | Knock Docs
I assume there can be workarounds, this is my first time messing around in the mobile builder, but I’d really prefer not to take workarounds when a react native sdk is available from them.