feat: Add Expo example with New Architecture support

.circleci/config.yml

@@ -124,7 +124,7 @@ jobs:
           command: curl -Ls "https://get.maestro.mobile.dev" | bash
 
       - run:
-          working_directory: example/test
+          working_directory: examples/example/test
           name: Build android
           command: yarn run build:android
 
@@ -141,10 +141,10 @@ jobs:
       - run:
           name: Install app on emulator
           command: |
-            adb install -r ~/project/example/android/app/build/outputs/apk/release/app-release.apk
+            adb install -r ~/project/examples/example/android/app/build/outputs/apk/release/app-release.apk
 
       - run:
-          working_directory: example/test
+          working_directory: examples/example/test
           name: Run UI Tests
           command: yarn run test:android
 
@@ -161,25 +161,25 @@ jobs:
       - <<: *setup_env_file
 
       - run:
-          working_directory: example/e2e
+          working_directory: examples/example/e2e
           name: Install Maestro
           command: curl -Ls "https://get.maestro.mobile.dev" | bash
 
       - restore_cache:
           keys:
-            - pod-dependencies-{{ checksum "~/project/example/ios/Podfile" }}
+            - pod-dependencies-{{ checksum "~/project/examples/example/ios/Podfile" }}
       - run:
-          working_directory: example/ios
+          working_directory: examples/example/ios
           name: Install Pods
           command: pod install
 
       - save_cache:
-          key: pod-dependencies-{{ checksum "~/project/example/ios/Podfile" }}
+          key: pod-dependencies-{{ checksum "~/project/examples/example/ios/Podfile" }}
           paths:
-            - ~/project/example/ios/Pods
+            - ~/project/examples/example/ios/Pods
 
       - run:
-          working_directory: example/test
+          working_directory: examples/example/test
           name: Build
           command: yarn run build:ios
 
@@ -193,10 +193,10 @@ jobs:
       - run:
           name: Install app on simulator
           command: |
-            xcrun simctl install booted ~/project/example/test/build/Build/Products/Release-iphonesimulator/IntercomReactNativeExampleUI.app
+            xcrun simctl install booted ~/project/examples/example/test/build/Build/Products/Release-iphonesimulator/IntercomReactNativeExampleUI.app
 
       - run:
-          working_directory: example/test
+          working_directory: examples/example/test
           name: Run UI Tests
           command: yarn run test:ios
 

.github/labeler.yml

@@ -1,2 +1,2 @@
 team-messenger:
- - base-branch: 'main'
+  - base-branch: 'main'

.github/workflows/labeler.yml

@@ -1,4 +1,4 @@
-name: "Pull Request Labeler"
+name: 'Pull Request Labeler'
 on:
   - pull_request_target
 
@@ -9,4 +9,4 @@ jobs:
       pull-requests: write
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/labeler@v5
+      - uses: actions/labeler@v5

.gitignore

@@ -41,11 +41,11 @@ local.properties
 android.iml
 
 # Ruby
-example/vendor/
+examples/*/vendor/
 
 # Cocoapods
 #
-example/ios/Pods
+examples/*/ios/Pods
 
 # node.js
 #

.yarnrc.yml

@@ -3,8 +3,8 @@ nmHoistingLimits: workspaces
 
 plugins:
   - path: .yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs
-    spec: "@yarnpkg/plugin-interactive-tools"
+    spec: '@yarnpkg/plugin-interactive-tools'
   - path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
-    spec: "@yarnpkg/plugin-workspace-tools"
+    spec: '@yarnpkg/plugin-workspace-tools'
 
 yarnPath: .yarn/releases/yarn-3.6.1.cjs

CONTRIBUTING.md

@@ -12,7 +12,12 @@ yarn
 
 > While it's possible to use [`npm`](https://github.com/npm/cli), the tooling is built around [`yarn`](https://classic.yarnpkg.com/), so you'll have an easier time if you use `yarn` for development.
 
-While developing, you can run the [example app](/example/) to test your changes. Any changes you make in your library's JavaScript code will be reflected in the example app without a rebuild. If you change any native code, then you'll need to rebuild the example app.
+While developing, you can run the example apps to test your changes:
+
+- **[Standard Example](/examples/example/)** - Full React Native app (Runs on Old React Native Architecture)
+- **[Expo Example](/examples/expo-example/)** - Expo-based app (Runs on New React Native Architecture)
+
+Any changes you make in your library's JavaScript code will be reflected in the example apps without a rebuild. If you change any native code, then you'll need to rebuild the example apps.
 
 To start the packager:
 
@@ -51,9 +56,9 @@ Remember to add tests for your change if possible. Run the unit tests by:
 yarn test
 ```
 
-To edit the Objective-C files, open `example/ios/IntercomReactNativeExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > intercom-react-native`.
+To edit the Objective-C files, open `examples/example/ios/IntercomReactNativeExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > intercom-react-native`.
 
-To edit the Kotlin files, open `example/android` in Android studio and find the source files at `intercomreactnative` under `Android`.
+To edit the Kotlin files, open `examples/example/android` in Android studio and find the source files at `intercomreactnative` under `Android`.
 
 ### Commit message convention
 
@@ -104,7 +109,7 @@ The `package.json` file contains various scripts for common tasks:
 
 When you're sending a pull request:
 
-### Make sure that Pull Request target is `dev` branch.
+### Make sure that Pull Request target is `dev` branch
 
 - Prefer small pull requests focused on one change.
 - Verify that linters and tests are passing.
@@ -188,11 +193,11 @@ Community leaders will follow these Community Impact Guidelines in determining t
 ### Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
 
 Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
 
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).