@symbiote-native/expo-modules-link 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -156,5 +156,5 @@ iOS Info.plist permission strings. iOS's own autolinking (`use_expo_modules!(exc
|
|
|
156
156
|
already auto-discovers every installed expo-modules-core package with zero per-package Podfile
|
|
157
157
|
edits once wired - see the `symbiote-expo-native-module` skill. The one-time per-app native
|
|
158
158
|
bootstrap (Podfile monkey-patch, `SymbioteExpoModulesFactory`, bridging header) is still a
|
|
159
|
-
manual, one-time step per app - this package only automates the
|
|
159
|
+
manual, one-time step per app - this package only automates the _recurring_ per-package
|
|
160
160
|
registration that repeats on every new native module.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@symbiote-native/expo-modules-link",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"description": "Native-module registration for apps using expo-modules-core wrapper packages (sensors, local-auth, haptics, ...). One app-level postinstall scans node_modules for every installed package's native-link.json and regenerates the app's app/build.gradle and MainApplication.kt registration blocks, so a new native module never needs a hand-edit.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|